Inherit shared settings across object renderer sets to avoid duplicate configuration

Admins want to define shared settings once at a base level and have them inherited by all object renderer sets, so that common configuration does not need to be duplicated and maintained separately in every set. Problem / Pain: Object renderer sets currently have no inheritance logic. Settings that are not role-specific, such as page size or other shared display options, must be defined individually in every set. In practice this leads to significant amounts of duplicate configuration that must be kept in sync manually across all current and future sets. Any change to a shared setting requires updating every set separately, which is time-consuming and error-prone. Impact / Benefit: Inheritance for object renderer sets would allow admins to define shared settings once at a base level and have them automatically apply across all sets that do not explicitly override them. This would dramatically reduce duplicate configuration, lower maintenance effort, and make it much easier to introduce changes consistently especially in modules with many sets or complex configurations. Example use case: An admin manages a module with multiple object renderer sets for different roles. All sets share the same page size configuration, which is not role-dependent. Currently this setting must be defined and updated separately in every set. With inheritance, the page size would be defined once at the base level and automatically apply to all sets — only role-specific overrides would need to be maintained individually. Idea source: Partner feedback Voting note: Vote for this idea if this need is relevant to you as well.