chore: rebase master onto main, merge master into main, delete master

[MantisClone]

@coderabbitai ignore

Problem

After GITBOOK-132: chore: sync FAQ changes from CR130 to Github, the Gitbook sync configuration was accidentally set to the master branch instead of the main branch.

As a result:

• main branch is still the default branch in Github but it's missing the latest changes (GITBOOK-133 through GITBOOK-140).
• master branch commit history is fully distinct from main and cannot be merged via the Github UI.
• Changes to the main branch are not synced with Gitbook and therefore are not deployed to https://docs.request.network.

This was discovered after merging #101, and the change was not deployed, contrary to expectations.

Solution

• Rebase master on top of main so that the git history is approximately correct.
• Push a new branch rebase-master-on-top-of-main
• Create pull request to merge rebase-master-on-top-of-main into main
• Allow Gitbook to bypass Github main branch protection rule
• Merge the pull request to main
• Fix Gitbook sync configuration to use main instead of master and initiate a resync.
• Delete master branch

[MantisClone]

I allowed Gitbook to bypass main branch protection rule. ✅

[bassgeta]

Changes seem sensible, time to get rid of master!
Nice pickup 😎

[MantisClone]

Received error:
https://gitbook.com/docs/getting-started/git-sync/troubleshooting

[MantisClone]

All action items have been completed and the problem is resolved. ✅