feat(doc): add guidance for developers about using autoware evaluator

[brkay54]

Description

Related issue:

• Add docs for guiding the developers on finding, diagnosing, and fixing scenarios in Autoware #548

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 Reviewers must check the checkboxes below before approval.

• The PR follows the pull request guidelines.

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.

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

[brkay54]

@xmfcx I used the Others section for this documentation but I couldn't be sure if it is the correct place or not.

[github-actions]

Documentation URL: https://autowarefoundation.github.io/autoware-documentation/pr-562/
Modified URLs:

• https://autowarefoundation.github.io/autoware-documentation/pr-562/how-to-guides/others/planning-evaluation-using-scenarios/

[brkay54]

cc @xmfcx @mitsudome-r
Hi,
The document is ready for review, but there are some blockers:

1. Regression Test Procedures:

   • In the issue created by Fatih, one of the conditions was: Procedures for running regression tests to ensure no disruptions are described.
   • To achieve this, we must download all scenarios from Autoware Evaluator to run them locally. However, during our discussion with Igata-san in the ODD WG, we decided this wouldn't be feasible because map versions in the cloud can vary, and a scenario depends not only on the map but also on its specific version.
   • Alternatively, developers can execute tests in the cloud for their PRs using Autoware Evaluator.

2. Access to the AWF Project:

   • We discussed with @mitsudome-r -san in previous weeks that the AWF Project will be made public (accessible without login), but this hasn't been implemented yet. Once it is, I may need to update the documentation links. Currently, this process is mentioned as Under Development in the documentation.

Except for these points, the document is ready for review. If there is any missing point or possible improvement, let me know.

[brkay54]

cc @xmfcx @mitsudome-r
After we discussed with Igata-san how people should be invited to the AWF project, I updated the documentation. Until make the AWF project more open, we decided to ask the new user to join ODD WG once to share his/her interest for now (Because of the AWF project's limited resources).
Currently, this PR is ready for review.

[ahmeddesokyebrahim]

Thanks so much @brkay54 for the amazing efforts and the very useful documentation.
The documentation is easy to follow and very descriptive.
I have some minor comments that would be better to have a look to them before merging your PR.
Thanks again and let me know if you have any thoughts for my comments.

[xmfcx]

Let's merge, any additional changes can be made in a separate PR.

Thanks for everyone's work.