Create seperate permission for adding field inheritance

Moving to 3.x branch. Considered as stable blocker.

Postponing on 📌 Store relation with the parent entity in the database instead of the State API Active . We might not need this one if the other goes in.

After 📌 Store relation with the parent entity in the database instead of the State API Active , the Field Inheritance form is a field widget. And we can use the widget visibility rules for this.
Also, other contrib modules like Field Permissions can help to add more granularity.