Enable searchSetId for reference field renderer

Allow reference field renderers to use a searchSetId, similar to subpanels. This would make it easier to reuse search settings across relations and apply different settings depending on where a reference field is used. Problem / Pain In subpanels, e.g. the following entry can be added to a layout: produktsupplement_ref We can then use the ID entered in the Object Renderer Set to determine a specific search renderer. The same ID can be used for different subpanels, even with different relations, if the same search and settings apply. Different settings can also be used for the same relation field in different subpanels. For reference fields in field renderers, the same approach is not available. An Object Renderer Set entry is required for each relation field, so the same settings may need to be entered again for relation fields to other modules. For one relation in one module, the same settings must be used unless different relation fields are created. This can make Object Renderer Sets longer and more complex. Impact / Benefit Supporting a searchSetId for reference field renderers would reduce duplicate configuration and make Object Renderer Sets easier to maintain. It would also provide more flexibility when the same relation is used in different contexts. Example use case Different object types are used in a product structure, for example for product categories and individual products. The settings for these subpanels can be defined in the subpanels of the objects. To link files from the file module, we must create a reference field for each object type and enter the settings for each relation into the Object Renderer Set. In this example, we could have two entries for both subpanels and reference fields. Currently, we need four entries. If we want to have a relation to another module (e.g. collections), we would need two more entries, and so on.