Add Permissions to Ultralytics Actions format.yml

[glenn-jocher]

This pull request significantly enhances the Ultralytics Actions workflow, introducing permissions for security best practices, alongside intelligent issue and PR handling. This includes automatic labeling, spam detection, abuse identification, and off-topic filtering. These updates ensure a more efficient and organized workflow, adhering to the latest Ultralytics standards.

🛠️ PR Summary

_{Made with ❤️ by Ultralytics Actions}

🌟 Summary

Improved the GitHub workflow to enhance code formatting, labeling, and PR summaries using updated Ultralytics Actions. 🚀

📊 Key Changes

• Updated the workflow to use the latest Ultralytics Actions for formatting and automation.
• Added explicit permissions for modifying code, PRs, and issues.
• Enhanced automation: now supports AI-powered labeling, Python formatting, spelling checks, and AI-generated PR summaries.
• Introduced support for additional API keys (OpenAI and Brave) to improve summaries and link checking.

🎯 Purpose & Impact

• Ensures code and documentation are consistently formatted to Ultralytics standards. 🧹
• Automates labeling and summary generation, making PR reviews faster and more informative. 🤖
• Improves overall code quality and project organization, benefiting both contributors and maintainers. 👥
• Reduces manual effort, allowing developers to focus more on building features and less on administrative tasks. ⏱️

[UltralyticsAssistant]

👋 Hello @glenn-jocher, thank you for submitting an ultralytics/flickr_scraper 🚀 PR! To ensure a seamless integration of your work, please review the following checklist:

• ✅ Define a Purpose: Clearly explain the purpose of your fix or feature in your PR description, and link to any relevant issues. Ensure your commit messages are clear, concise, and adhere to the project's conventions.
• ✅ Synchronize with Source: Confirm your PR is synchronized with the ultralytics/flickr_scraper main branch. If it's behind, update it by clicking the 'Update branch' button or by running git pull and git merge main locally.
• ✅ Ensure CI Checks Pass: Verify all Ultralytics Continuous Integration (CI) checks are passing. If any checks fail, please address the issues.
• ✅ Update Documentation: Update the relevant documentation for any new or modified features.
• ✅ Add Tests: If applicable, include or update tests to cover your changes, and confirm that all tests are passing.
• ✅ Sign the CLA: Please ensure you have signed our Contributor License Agreement if this is your first Ultralytics PR by writing "I have read the CLA Document and I sign the CLA" in a new message.
• ✅ Minimize Changes: Limit your changes to the minimum necessary for your bug fix or feature addition. "It is not daily increase but daily decrease, hack away the unessential. The closer to the source, the less wastage there is." — Bruce Lee

For more guidance, please refer to our Contributing Guide. Don’t hesitate to leave a comment if you have any questions. Thank you for contributing to Ultralytics! 🚀

This is an automated response — an Ultralytics engineer will review your PR and assist further soon. 😊

[UltralyticsAssistant]

Fantastic work, @glenn-jocher! 🚀 As Thomas Edison once said, "Genius is one percent inspiration and ninety-nine percent perspiration." Your dedication to streamlining our workflows with enhanced Ultralytics Actions truly embodies this spirit. These improvements not only elevate our code quality and efficiency but also empower the community to innovate faster on Ultralytics HUB and beyond. Thank you for your impactful contributions—your efforts make all the difference!