Fix Docs links

[AndersonQ]

What does this PR do?

Reverts the Docs link from BEATNAME/modules.d/MODULE.yml.disabled to use master instead of main introduced by #35226.
It also reverts #35693 as it did not fix the problem.

Why is it important?

The links are broken

Checklist

• [ ] My code follows the style guidelines of this project
• [ ] I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• [ ] I have made corresponding change to the default configuration files
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

• Relates [Release] Update docs for the 8.9.0 release #35226
• Closes https://github.com/elastic/ingest-dev/issues/2111

[elasticmachine]

Pinging @elastic/elastic-agent (Team:Elastic-Agent)

[elasticmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2023-06-12T13:35:56.591+0000

• Duration: 112 min 54 sec

Test stats 🧪

Test	Results
Failed	0
Passed	27337
Skipped	2009
Total	29346

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

• /package : Generate the packages and run the E2E tests.

• /beats-tester : Run the installation tests with beats-tester.

• run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

[AndersonQ]

@cmacknz could you force merge it? the check not passing is the linter complaining about things I did not change :/

[cmacknz]

You are blocked by the code owner check from SEI. The lint check failing doesn't block merge.

Waiting on code owner review from elastic/security-external-integrations