NOISSUE - Rename Magistrala to SuperMQ in docs repo

[Musilah]

Pull request title should be MG-XXX - description or NOISSUE - description where XXX is ID of issue that this PR relate to.
Please review the CONTRIBUTING.md file for detailed contributing guidelines.

What does this do?

This PR renames the magistrala docs to superMQ

Which issue(s) does this PR fix/relate to?

Put here Resolves #XXX to auto-close the issue that your PR fixes (if such)
N/A

List any changes that modify/break current functionality

• Rename Magistrala to SuperMQ in the Docs
• Update links and images for SuperMQ
• Switch to Docusaurus for Documentation from MkDocs
• Update the Homepage and Blogs for new Docusaurus

Have you included tests for your changes?

No

Did you document any new/modified functionality?

Yes

Notes

New SuperMQ docs Homepage:

Docs Page with sidebar:

Blogs page:

[wambui-pixel]

Logo is too small

[wambui-pixel]

the on-hover is a bit too dark

[wambui-pixel]

1. The logo is bigger in dark mode
2. The active color is not easily visible

[wambui-pixel]

1. Increase the size, especially of the home logo
2. This font headers look a bit off.
3. We should switch this image to one that uses superMQ, and not Mainflux

[felixgateru]

check whether you can have this rendered as go code similar to what is in mkdocs as well as other instances

[dborovcanin]

Rename The Scalable, Secure IoT Cloud Platform to Event-driven Infrastructure for Modern Cloud and Scalable IoT Middleware to Scalable Messaging Middleware.

[dborovcanin]

Group the sidebar in the following manner:

Overview

Architecture

Concepts

• Entities
• Authentication
• Authorization
• Security
• Messaging

Getting Started

• API
• CLI

Developer's guide

• Events
• Tracing

Storage

Edge

Certs

Kubernetes

SMQ-Contrib Repository

• LoRa
• OPC-UA
• Provision
• Twins Service
• Bootstrap

Test Spec

Also, please update Storage links, since some of those addons are now in the contrib repo.

[dborovcanin]

Please change section titles to avoid duplications:

Something like Overview will work, but try to think of something better, ideally different for each subsection.