Create "Rabbit Hole" field type for overrides

I'll work on this during #LutskGCW23

'Rabbit hole' field type and appropriate widget is implemented.
Field formatter can be skipped because without it field still works fine but is disabled at 'Manage display' page.

alt.dev → made their first commit to this issue’s fork.

Reviewed and tested the current solution.
Fixed a couple of bugs I found.

The issue is a blocker for another ticket - 📌 Use Rabbit Hole values from config field instead of base fields Fixed , and possibly for 📌 Automatically copy values from old base fields to new config field Fixed

Reviewed and tested the current solution.
Fixed a couple of bugs I found.

The issue is a blocker for another ticket - 📌 Use Rabbit Hole values from config field instead of base fields Fixed , and possibly for 📌 Automatically copy values from old base fields to new config field Fixed

@matroskeen One thing to think about, at the moment the allow_override option is enabled by default (to keep the previous behavior), but since we want to avoid unnecessary field creation, it would be nice if this option was disabled by default.
This is just a thought out loud.

@HitchShock thanks for picking this up! Let's change the behavior and keep allow_override disabled by default.
I also added some comments to the merge request, so it's back to "Needs Work".

@matroskeen About allow_override - it should be a separate issue. See my comment here

@HitchShock I agree it can be another issue. I suggested expanding the scope of 📌 Use Rabbit Hole values from config field instead of base fields Fixed , but feel free to create a new one if it makes sense. I also made more detailed review and added more comments to the MR.

Thank you and keep up the good work!

Thanks everyone for your hard work! Special kudos to @HitchShock for keeping it up!
We can advance to the next step, which is: 📌 Use Rabbit Hole values from config field instead of base fields Fixed .

Automatically closed - issue fixed for 2 weeks with no activity.