Migration of rules metadata to common rules specification

[zippy1978]

This PR includes support for the common ecoCode rules repository (https://github.com/green-code-initiative/ecoCode/tree/main/ecocode-rules-specifications)

As a consequence existing local rule key/ids are changed. Example: ESOB002 rule becomes EC19.

Defining local rules is still supported, and useful for when working on a rule which is not released in the common repo yet. ESOB007 is such a rule (new rule not in common repo yet).

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud

[dedece35]

This PR includes support for the common ecoCode rules repository (https://github.com/green-code-initiative/ecoCode/tree/main/ecocode-rules-specifications)

As a consequence existing local rule key/ids are changed.

Example: ESOB002 rule becomes EC19.

Defining local rules is still supported, and useful for when working on a rule which is not released in the common repo yet.

ESOB007 is such a rule (new rule not in common repo yet).

do you want me to create a new release of ecocode-rules-specifications ? is all ok in this project for you to build correctly ios repo ?

[zippy1978]

@dedece35, PR is ok with local up to date ecocode-rules-specifications. It will be mergeable s soon as a new version of ecocode-rules-specifications is released (would be good to merge it before the 2024 challenge)

[zippy1978]

This PR is waiting for a new ecocode-rules-specifications release to pass.

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud