Update MkDocs and documentation preparing for v3.0 release

[mossmaurice]

Notes for Reviewer

• Update MkDocs and documentation preparing for v3.0 release

  • Update version of MkDocs material related packages
  • Fix HTML footer

• ToDo

  • Check all links => Proposal: only to be merged on release_3.0 branch
  • Run iceoryx_release.sh in
  • Review all exisiting articles
  • Go through items in Release validation for v3.0 #1295
  • Create release branch release_3.0
  • Write release notes
  • Check ascinema recordings
  • Prepare ROS 2 release

Pre-Review Checklist for the PR Author

1. Code follows the coding style of CONTRIBUTING.md
2. Tests follow the best practice for testing
3. Changelog updated in the unreleased section including API breaking changes
4. Branch follows the naming format (iox-123-this-is-a-branch)
5. Commits messages are according to this guideline
   • Commit messages have the issue ID (iox-#123 commit text)
   • Commit author matches Eclipse Contributor Agreement (and ECA is signed)
6. Update the PR title
   • Follow the same conventions as for commit messages
   • Link to the relevant issue
7. Relevant issues are linked
8. Add sensible notes for the reviewer
9. All checks have passed (except task-list-completed)
10. Assign PR to reviewer

Checklist for the PR Reviewer

• Consider a second reviewer for complex new features or larger refactorings
• Commits are properly organized and messages are according to the guideline
• Code according to our coding style and naming conventions
• Unit tests have been written for new behavior
• Public API changes are documented via doxygen
• Copyright owner are updated in the changed files
• All touched (C/C++) source code files from iceoryx_hoofs have been added to ./clang-tidy-diff-scans.txt
• PR title describes the changes

Post-review Checklist for the PR Author

1. All open points are addressed and tracked via issues

References

• Closes Release validation for v3.0 #1295

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 78.68%. Comparing base (f33d582) to head (bbf7136).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2398   +/-   ##
=======================================
  Coverage   78.68%   78.68%           
=======================================
  Files         440      440           
  Lines       16986    16986           
  Branches     2361     2361           
=======================================
  Hits        13365    13365           
  Misses       2740     2740           
  Partials      881      881           

Flag	Coverage Δ
unittests	78.48% <ø> (ø)
unittests_timing	15.35% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[mossmaurice]

@elBoberido Ready for review. The documentation is completely fixed. Please do the full review on this PR. Once the findings are addressed I'll merge only the commits without (DROP ME) to main and then create the release_3.0 branch. I'll open a separate PR with the (DROP ME) changes against release_3.0. Does that make sense to you?

[mossmaurice]

@elBoberido

This is the short summary of the release. I will re-use this for the release description on GitHub and on Eclipse. Please check if anything major is missing.