Restructuring ROS 2 Gem docs

[adamdbrw]

Change summary

Improving structure and information efficiency of ROS 2 Gem documentation.

This is a DRAFT. Description of changes will be updated.

Submission Checklist:

• Descriptive active voice - Do descriptive sentences have a clear subject and action verb?
• Answer the question at hand - Does the documentation answer a what, why, how, or where type of question?
• Consistency - Does the content consistently follow the Style Guide?
• Help the user - Does the documentation show the user something meaningful?

[chanmosq]

@adamdbrw I've left some comments on the files. Here are some other changes to make:

• Rename ros2 directory to robotics and _index.md to ros2.md The Gem Reference directories are purposely high-level categories. You would also need to update the link in gems/reference/_index.md. (This is different from the initial instruction I gave you, apologies for the setback)
• Move class-diagram.md, concepts-and-components.md, and vehicle-dynamics.md to the subfolder interactivity/robotics. Only _index.md (soon-to-be ros2.md) should be in the gems/reference/robotics folder.
• I made various comments to fix the linkTitle, title, and description to follow the metadata guidelines.

[chanmosq]

The DCO issue seems to point to 777ef82, a commit on this branch.
To resolve this, you can take one of the remediation steps outlined in the DCO check. (You can also find this page by clicking Details next to "DCO" at the bottom of a PR.)

I talked about this with @michalpelka as well and we've resolve the issue so this shouldn't happen anymore. In case this happens again for another team member, to summarize, the issue is because of different name and email configurations. The Git's web interface profile configuration is set to Michał Pełka <michalpelka@gmail.com> and the local git install configuration is set to Michał Pełka <michal.pelka@robotec.ai>. They must be exactly the same because that's how Git verifies that the committer is signed by the right person.

[adamdbrw]

All comments should be applied now. I think that the DCO issue resolved itself due to rebase (the culprit commit is actually not from the branch and the issue was resolved in upstream development). @chanmosq I also un-drafted the PR. @michalpelka could you review it as well and see if it works for you?

[hultonha]

This updates look great to me, awesome work @adamdbrw 🥳

Remove approval for change to be made, but didn't request changes to avoid blocking

[wojtek-robotecai]

Take a look at my comments and suggestions

[adamdbrw]

@chanmosq is there anything else we could do to proceed with the merge of this PR?

[adamdbrw]

@chanmosq I applied all the comments. I made some minor changes to reflect semantics.

[chanmosq]

Looks great! Thanks @adamdbrw @michalpelka and @wojtek-robotecai