Enhance GeoFence attribute rule

[dsuren1]

Description

We have to provide a small but really useful improvement for the GeoFence Rule Manager in MS.
At the moment, when a rule is created, the tab for the attributes has the DDs set to READ ONLY by default but only the constraints on the attributes for which the user has manually changed the status of the DD are sent: the others ones are not sent to GeoFence when the rule is saved in the UI.
This often generates misunderstandings as the user thinks that the other constraints on the attributes besides the modified ones are set but instead they are not and GeoFence consequently denies write access to certain attributes configured by the user if also grant for other attribute are not specified.

Acceptance criteria

• The attributes access type/constraints DD values should show only the following list of options NONE, READONLY, READWRITE.
• When the attributes is enabled, upon saving the rule, the attributes along with constraints are sent in the payload
  • This is applicable regardless of whether the user makes a change to a particular attribute
  • All the attributes with currently selected constraints/access types in the UI are sent in the payload to be persisted (save/update)
• The attributes and respective constraints/access type should always match the value persisted in the backend
• Default access type is READONLY

What kind of improvement you want to add? (check one with "x", remove the others)

• Enhancement

Other useful information

Ref: https://github.com/geosolutions-it/MapStore2-C040/issues/459

[tdipisa]

Waiting 2024.01.00 before backporting connected PR.