#10111: Enhance GeoFence attribute rule

[dsuren1]

Description

This PR enhances the attributes rules editor

Please check if the PR fulfills these requirements

• The commit message follows our guidelines: https://github.com/geosolutions-it/MapStore2/blob/master/CONTRIBUTING.md
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce? (check one with "x", remove the others)

• Enhancement

Issue

What is the current behavior?

• Enhance GeoFence attribute rule #10111

What is the new behavior?
Allows user

• To save all the attributes with default value (READONLY)
• To update the specific attributes while retaining the existing changes reflective of the DB
• Fix payload object causing failure on POST

Breaking change

Does this PR introduce a breaking change? (check one with "x", remove the other)

• Yes, and I documented them in migration notes
• No

Other useful information

[offtherailz]

It works as expected.
Tests performed:

• On rule creation, all the attrbutes are set to read-only, if nothing changes.
• A second edit is persisted correctly.

[offtherailz]

@tdipisa I think next steps are backport and installation in test env c040
Testing it on mapstore dev instance is impossible because it requires the geofence stand-alone.

[tdipisa]

@ElenaGallo @dsuren1 this is for 2024.01.01 therefore let's wait the delivery of 2024.01.00 before backporting this. Thank you.

[ElenaGallo]

@dsuren1 @tdipisa When the user with access rule for a layer opens the attribute table, he has edit permission

How to Reproduce

• Login as admin
• Create this rule:
  
• Create this sondaggi map
• Login as geosolutions_test
• Open this sondaggi map
• Select V_SONDAGGI layer
• Open the Attribute Table
  -> the Edit button is present on the attribute table

[tdipisa]

@ElenaGallo

@dsuren1 @tdipisa When the user with access rule for a layer opens the attribute table, he has edit permission

Why it should not be? This depends on how you decide to configure the plugin. In any case, I'm sorry but, it seems totally unrelated to the scope of this PR. Did you understand what to test here? The PR description seems quite clear to me.

[ElenaGallo]

Test passed, @dsuren1 please backport to 2024.01.xx

[tdipisa]

@dsuren1 this still need to be backported for 2024.01.01