Update and Consolidate Communication Channels in Documentation

[SweilemCodes]

Summary

The documentation currently lists Freenode IRC and a mailing list as primary communication channels, but these are outdated and no longer active. To improve clarity and accessibility, it would be helpful to compile all official support and communication channels into one central, up-to-date location.

Some recommended topics to cover:

• Update Official Support & Communication Channels
• Add Links to Communication Channels
• (Potentially) Compilation of the proper e-mails/contacts where people can seek support for cases that aren't appropriate for conventional channels, such as finding a vulnerability within the framework.

Motivation

We should document this to ensure that users and contributors can easily find accurate information on how to get support and engage with the Metasploit community.

Steps To Resolve This Issue

1. Identify all outdated references to Freenode IRC and/or the metasploit-hackers mailing list

Here are some that I could find:

• readme.md - support and communication
• contact.md / contact.html
• Rapid7 Getting Support
• Rapid7 IRC Instructions

2. Determine the current official support and/or communication channels (there are likely more)

Primary Platforms:

• Discussion Tab
• IRC? (Couldn't find an announcement about a switch)
• Slack
• GitHub
• Twitter
• Mastodon

Passive Channels:

• Rapid7 Blog - Metasploit Tag

Unofficial Channels:

• Reddit

3. Update the documentation (that we can) and follow the established format and style.

• Overview on contributing module documentation
• Docs Templates

4. Open a pull request including the words "closes #[this issue's number]" in the pull request description.

[jphamgithub]

Hi! I've submitted PR #20429 to address this issue. The changes update the communication channels across README.md, Contact.md, and CONTRIBUTING.md as outlined in your detailed steps. I followed the established format and style, and included GitHub Discussions and Slack as primary channels while maintaining references to existing IRC and mailing lists. Thanks for the clear guidance. I think this at least moves the needle forward to close this issue?