BaseFieldOverride cause inconsistencies during export

I noticed 🐛 Make BaseFieldOverride inherit internal property from the base field Fixed fixed isInternal() for BaseFieldOverride in core 10.1.6
I believe it should address point 1 but not point 2 (from #9).
Is my assumption correct in the first place? that we want to skip internal and read-only fields but not computed

removing the revision affected field seems sensible, that is calculated on save anyway. Should be updated to a merge request to verify that tests still pass.

The IS is no longer accurate since 🐛 Make BaseFieldOverride inherit internal property from the base field Fixed fixed isInternal for BaseFieldOverride and path aliases are now exported.
But maybe we could use this issue to discard fields that are marked as read-only?
I created a MR, anyway.

This is a great fix. Lots of hardcoded overrides removed and works a treat. I'm using this MR on a site with exported commerce products & variations and it cleans up a load of stuff.