[CHEF-10965] Fixing bundler config syntax change in bundler > v2.1

[RoyShravani]

🔩 Description: What code changed, and why?

Fixing bundler config syntax change in bundler > v2.1

Ruby 3.0.1 came with Bundler 2.1.x (likely Bundler 2.1.4 or similar) where Bundler introduced several new features and improvements, one of which was syntactical change in the bundle config command.
With upgrade to Ruby 3.0.1 in Infra-server (ocid) 15.8.0 bundler doesn’t recognise this older command and ignores the local configuration and creates the ./bundle at the root which is the default bundler behaviour as we need to run automate as a root user.
This creates conflict with global environment variables like GEM_PATH and GEM_HOME.

⛓️ Related Resources

👍 Definition of Done

👟 How to Build and Test the Change

✅ Checklist

All PRs must tick these:

• I have read the CONTRIBUTING document.
• All commits signed-off for the Developer Certification of Origin.

With occasional exceptions, all PRs from Progress employees must tick these:

• Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
• Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
• Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
• Spelling, grammar, typos checked? (at a minimum use make spell in any component directory)
• Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)

All PRs from Progress employees should tick these if appropriate:

• Tests added/updated? (all new code needs new tests)
• Docs added/updated? (all customer-facing changes)

Please add a note next to any checkbox above if you are NOT ticking it.

📷 Screenshots, if applicable

[netlify]

👷 Deploy Preview for chef-automate processing.

Name	Link
🔨 Latest commit	c06bd23
🔍 Latest deploy log	https://app.netlify.com/sites/chef-automate/deploys/678915a9e42b7500086a616d

[sonarqube-for-infrastructure-prod]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube