Remove Slack references from documentation and website

[Copilot]

Removes all Slack channel references (slack.steeltoe.io, steeltoeteam.slack.com) from documentation and website codebase. Other support channels (GitHub, Stack Overflow, Twitter/X, NuGet) remain unchanged.

Changes

Website components:

• Support.razor - Removed Slack feature card from support options
• Community.razor - Removed Slack section with icon, links, and troubleshooting text
• Why-Steeltoe.razor - Removed Slack mention from "Steeltoe is supportive" description

Documentation:

• docs/guides/get-to-know-steeltoe/summary.md - Removed Slack from support list
• docs/docs/v3/bootstrap/index.md - Removed Slack from feedback section
• docs/docs/v4/bootstrap/app-bootstrap.md - Removed Slack from feedback section
• docs/articles/releases/steeltoe-4-0-0-rc1.md - Removed Slack bullet from "Try It Out" section
• docs/articles/steeltoe-3-2-2-adds-kube-service-bindings.md - Removed Slack reference from closing paragraph

Before:

Let us know by [filing an issue](https://github.com/SteeltoeOSS/Steeltoe/issues/new/choose), [joining us on Slack](https://slack.steeltoe.io/) or [tagging us on Twitter/X](https://x.com/steeltoeoss).

After:

Let us know by [filing an issue](https://github.com/SteeltoeOSS/Steeltoe/issues/new/choose) or [tagging us on Twitter/X](https://x.com/steeltoeoss).

Original prompt

Summary

Remove all references to Slack from the documentation and website codebase.

Files to Update

Based on code search, the following files contain Slack references that need to be removed or updated:

1. docs/guides/get-to-know-steeltoe/summary.md

• Remove the line - Slack (https://slack.steeltoe.io) from the Support section

2. docs/docs/v3/bootstrap/index.md

• Update the feedback section at the bottom - remove the text [joining us on Slack](https://slack.steeltoe.io/) or from the line:

  Let us know by filing an issue, joining us on Slack or tagging us on Twitter/X.

3. src/Steeltoe.io/Components/Pages/Support.razor

• Remove the entire Slack feature block (the first new() block in the _features array that has Title = (MarkupString)"Slack")

4. src/Steeltoe.io/Components/Pages/Community.razor

• Remove the Slack section including:
  • The bi bi-slack div
  • The Steeltoe Slack link
  • The description paragraph about Slack
  • The troubleshooting text with alternative join link and email

5. docs/articles/releases/steeltoe-4-0-0-rc1.md

• Remove the line * 🔗 Ask questions and join the conversation on [Slack](https://slack.steeltoe.io/)

6. docs/docs/v4/bootstrap/app-bootstrap.md

• Update the feedback section at the bottom - remove the text [joining us on Slack](https://slack.steeltoe.io/) or from the line:

  Let us know by filing an issue, joining us on Slack or tagging us on Twitter/X.

7. docs/articles/steeltoe-3-2-2-adds-kube-service-bindings.md

• Remove/update the sentence at the end: "Remember you can join us on the Steeltoe Community call or reach out to the team directly on the Steeltoe Slack."
• Either remove this sentence entirely or remove just the Slack reference portion

8. src/Steeltoe.io/Components/Pages/Why-Steeltoe.razor

• In the "Steeltoe is supportive" section, remove the reference to Slack in the description:

  "...support, and even access to the development team on Slack."

• Change to something like: "...support, and even access to the development team."

Notes

• Ensure grammar and formatting remain correct after removals
• Keep other support channels (GitHub, Stack Overflow, Twitter/X, NuGet) intact
• There may be additional files not caught by the initial search - please search thoroughly for any other Slack references (including slack.steeltoe.io, steeltoeteam.slack.com, bi-slack, etc.)

This pull request was created from Copilot chat.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[TimHess]

This section is a little weird now, I wonder about removing this whole line now, but I'm not sure how far we should go editing an old blog post