feat(lanelet2_map_validator): added issue codes

[TaikiYamada4]

Description

This PR adds issue codes to the validator so that systems receiving the JSON output can process the issues much mechanically.

The issue codes are automatically generated by taking the upper snake case of the validator's name and remove the first Mapping. part.

I also added the issue codes to the documents.

Related links

None

Tests performed

Updated the test codes to check that the autoware_lanelet2_map_validator outputs the correct issue codes, and confirmed that colcon test passes.

Normal validation like

ros2 run autoware_lanelet2_map_validator autoware_lanelet2_map_validator -p mgrs -m ./src/universe/autoware.universe/common/autoware_test_utils/test_map/lanelet2_map.osm -i ./src/autoware_tools/map/autoware_lanelet2_map_validator/autoware_requirement_set.json -o ./

will return lanelet2_validation_results.json like this.

{
    "requirements": [
        {
            "id": "vm-02-02",
            "passed": true,
            "validators": [
                {
                    "name": "mapping.stop_line.missing_regulatory_elements",
                    "passed": true
                }
            ]
        },
        {
            "id": "vm-04-01",
            "passed": false,
            "validators": [
                {
                    "issues": [
                        {
                            "id": 163,
                            "issue_code": "Crosswalk.MissingRegulatoryElements-001",
                            "message": "No regulatory element refers to this crosswalk.",
                            "primitive": "lanelet",
                            "severity": "Error"
                        },
                        {
                            "id": 164,
                            "issue_code": "Crosswalk.MissingRegulatoryElements-001",
                            "message": "No regulatory element refers to this crosswalk.",
                            "primitive": "lanelet",
                            "severity": "Error"
                        },
                        {
                            "id": 165,
                            "issue_code": "Crosswalk.MissingRegulatoryElements-001",
                            "message": "No regulatory element refers to this crosswalk.",
                            "primitive": "lanelet",
                            "severity": "Error"
                        },
                        {
                            "id": 166,
                            "issue_code": "Crosswalk.MissingRegulatoryElements-001",
                            "message": "No regulatory element refers to this crosswalk.",
                            "primitive": "lanelet",
                            "severity": "Error"
                        }
                    ],
                    "name": "mapping.crosswalk.missing_regulatory_elements",
                    "passed": false
                },
                {
                    "name": "mapping.crosswalk.regulatory_element_details",
                    "passed": true,
                    "prerequisites": [
                        {
                            "name": "mapping.crosswalk.missing_regulatory_elements"
                        }
                    ]
                }
            ]
        },
        {
            "id": "vm-05-01",
            "passed": false,
            "validators": [
                {
                    "name": "mapping.traffic_light.missing_regulatory_elements",
                    "passed": true
                },
                {
                    "issues": [
                        {
                            "id": 9896,
                            "issue_code": "TrafficLight.RegulatoryElementDetails-001",
                            "message": "Regulatory element of traffic light must have a stop line(ref_line).",
                            "primitive": "regulatory element",
                            "severity": "Error"
                        },
                        {
                            "id": 9918,
                            "issue_code": "TrafficLight.RegulatoryElementDetails-001",
                            "message": "Regulatory element of traffic light must have a stop line(ref_line).",
                            "primitive": "regulatory element",
                            "severity": "Error"
                        },
                        {
                            "id": 9838,
                            "issue_code": "TrafficLight.RegulatoryElementDetails-001",
                            "message": "Regulatory element of traffic light must have a stop line(ref_line).",
                            "primitive": "regulatory element",
                            "severity": "Error"
                        },
                        {
                            "id": 9874,
                            "issue_code": "TrafficLight.RegulatoryElementDetails-001",
                            "message": "Regulatory element of traffic light must have a stop line(ref_line).",
                            "primitive": "regulatory element",
                            "severity": "Error"
                        }
                    ],
                    "name": "mapping.traffic_light.regulatory_element_details",
                    "passed": false,
                    "prerequisites": [
                        {
                            "name": "mapping.traffic_light.missing_regulatory_elements"
                        }
                    ]
                }
            ]
        }
    ]
}

Notes for reviewers

Order of the issues is changed in some test codes and documents so that they match with its number, but I believe the content isn't changed.

Interface changes

The output JSON also contains the issue_code.

Effects on system behavior

Except the output shows issue codes, none.

Pre-review checklist for the PR author

The PR author must check the checkboxes below when creating the PR.

• I've confirmed the contribution guidelines.
• The PR follows the pull request guidelines.

In-review checklist for the PR reviewers

The PR reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.
• The PR has been properly tested.
• The PR has been reviewed by the code owners.

Post-review checklist for the PR author

The PR author must check the checkboxes below before merging.

• There are no open discussions or they are tracked via tickets.
• The PR is ready for merge.

After all checkboxes are checked, anyone who has write access can merge the PR.