Add a glossary to the Autoware documentation

[ghost]

There are a few ways in which we could approach this.

1. Implement a full glossary that explains acronyms (eg: HMI for Human Machine Interface) and commonly used terms that people new to Autoware and autonomous driving may not understand.
2. Implement a simple glossary for acronyms only. Mkdocs has functionality to add tooltips and to include arbitrary external files, such as a list of acronyms and their meanings.
3. A combination of the above.
4. Something completely different.

As the Autoware community grows, I think that it is important that we have a shared understanding of terms to reduce confusion and to help new members to get up to speed faster, and a glossary is one way in which we can work towards that goal.

[BonoloAWF]

This is a good idea!

[andrejpadilha2]

I like this! The full glossary is a good idea, but probably starting with a simple one is better. Maybe, for most acronyms, short explanations that could lead people to search a better explanation on their own. If it's something that the Autoware Community wants to explain in their own way, a full explanation can be added.