Add /vendor/bundle/ to .gitignore to exclude bundled dependencies

[Copilot]

This PR isolates the .gitignore modification that was mixed with other changes in a previous PR. The change adds /vendor/bundle/ to the .gitignore file to prevent locally bundled Ruby dependencies from being committed to the repository.

Problem

When using bundle install --path vendor/bundle or similar bundler configurations that install gems locally, the entire vendor/bundle/ directory gets created with thousands of gem files. Without proper gitignore rules, these dependency files can accidentally be committed, bloating the repository with third-party code that should not be tracked.

Solution

Added a single line /vendor/bundle/ to the .gitignore file to ensure that:

• Locally bundled gems are ignored by Git
• Developers can safely use bundle install --path vendor/bundle
• The repository stays clean of third-party dependency files
• Bundle configuration remains flexible for different development environments

Changes

• Modified: .gitignore - Added /vendor/bundle/ entry
• Removed: Previously committed vendor/bundle files that were accidentally included

Verification

• ✅ bundle install works correctly and creates vendor/bundle directory
• ✅ git status shows vendor/bundle is properly ignored
• ✅ All existing tests continue to pass
• ✅ Repository maintains clean state

This change follows standard Ruby/Rails gitignore practices and ensures that bundled dependencies are excluded from version control.

---

💡 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.