feat-ISSUE-3782-PR 1/2 adding crosstables rule - zone for destination and source

[Imat00]

• add crosstable rule_destination_to_zone and rule_source_to_zone
• add FKs for both to rule and zone
• update upgrade script 9.0
• update permissions + permissions for management and some rule_* tables

management - role reporter - select - add mgm_uid

rule - recertifier - select - add is_global and rulebase_id
rule - modeller - select - add is_global and rulebase_id

rule_from/rule_to - middleware - seelct - add cl_from_relevant_for_tenant
rule_service and more add removed in select for filtered roles

changelog_rule add cl_rule_relevant_for_tenant in select for filtered roles

[tpurschke]

@Imat00 sorry I also had to add some permissions - could you please resolve the resulting conflicts in your branch?
Feel free to reach out to me for any questions.

[Imat00]

@Imat00 sorry I also had to add some permissions - could you please resolve the resulting conflicts in your branch? Feel free to reach out to me for any questions.

should be done

[tpurschke]

@Imat00 there seems to be an issue with the metadata file (test import job fails)

[Imat00]

@Imat00 there seems to be an issue with the metadata file (test import job fails)

Yes, currently working on it

[Imat00]

Finally!
I think we should still check Permissions again.

[Y4nnikH]

I added the necessary changes in the importer and middleware to correctly handle multiple zones per rule source/destination. And I renamed the new tables to make it more consistent with existing similar tables.
We will add my changes into this branch before we merge the pr.

One note / inconsistency regarding the new tables: We now have a situation where we link to the crosstable rule_from_zone, like with rule_from via ids, but we do not write the zones directly into the rule as a string, like we do with rule_src. (same with rule_to_zone). This has the benefit, that we do not get a new rule version whenever the zones change. only the crosstable changes. But it would be more consistent if we also wrote the zones as string to each rule entry (or the other way around, remove the rule_src/dst/svc etc fields from the rule)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud