Add workflow to post gatorbot issues

[jeffsmale90]

📝 Description

New issues raised on the smart accounts kit are posted to slack via the gator bot.

Presently this posts all issues created. If this becomes noisy, we can consider filtering out issues created by team members.

🔄 What Changed?

List the specific changes made:

🚀 Why?

Explain the motivation behind these changes:

🧪 How to Test?

Describe how to test these changes:

• Manual testing steps:

• Automated tests added/updated
• All existing tests pass

⚠️ Breaking Changes

List any breaking changes:

• No breaking changes
• Breaking changes (describe below):

📋 Checklist

Check off completed items:

• Code follows the project's coding standards
• Self-review completed
• Documentation updated (if needed)
• Tests added/updated
• Changelog updated (if needed)
• All CI checks pass

🔗 Related Issues

Link to related issues:
Closes #
Related to #

📚 Additional Notes

Any additional information, concerns, or context:

---

Note

Low Risk
Low risk: adds a standalone GitHub Actions workflow that posts issue metadata to Slack via a secret webhook, with no runtime code changes. Main risk is misconfiguration/noise if the webhook secret is missing or points to the wrong channel.

Overview
Adds a new GitHub Actions workflow, new-issue-slack-notification.yml, that triggers on issues: opened and posts a formatted Slack message containing the issue title, author, and link.

The job uses the GATOR_BOT_SLACK_WEBHOOK_URL secret, fails fast when it’s unset, builds the payload with jq, and sends it via curl.

^{Reviewed by Cursor Bugbot for commit f63e8fe. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mj-kiwi]

Let's go