FIx kitchen test failures in windows boxes due to dependency issue in proxifier

[neha-p6]

Description

Kitchen tests on windows fail when installing gems with error:

1 gem installed
  Successfully built RubyGem
  Name: rest-client
  Version: 2.1.0
  File: rest-client-2.1.0.gem
Successfully installed rest-client-2.1.0
1 gem installed
WARNING:  licenses is empty, but is recommended.  Use a license identifier from
http://spdx.org/licenses or 'Nonstandard' for a nonstandard license.
WARNING:  See https://guides.rubygems.org/specification-reference/ for help
  Successfully built RubyGem
  Name: proxifier
  Version: 1.0.3
  File: proxifier-1.0.3.gem
ERROR:  Error installing proxifier-1.0.3.gem:
	"pirb" from proxifier conflicts with installed executable from proxifier2
post-bundle-install.rb:27:in `block (2 levels) in <main>': gem install failed (RuntimeError)
	from post-bundle-install.rb:25:in `chdir'
	from post-bundle-install.rb:25:in `block in <main>'
	from post-bundle-install.rb:11:in `each'
	from post-bundle-install.rb:11:in `<main>'
fixing bundle installed gems in C:/opscode/chef/embedded/lib/ruby/gems/3.1.0
re-installing ohai...
re-installing ohai...
re-installing rest-client...
re-installing proxifier...

(Ref https://github.com/chef/chef/actions/runs/4477841478/jobs/7869877395?pr=13643#step:5:65)

We used to pull proxifier from git repo but now it is getting pulled from rubygems itself.
But somehow github kitchen test windows boxes still have previously git downloaded entry for proxifier (the boxes are not cleaned up?) due to which post-bundle-install.rb tries to reinstall it resulting in dependency issues between proxifier and proxifier2.
The script post-bundle-install is specifically doing the job of re-installing gems which are pulled from git repos.
The bundler/gems directory on those windows boxes seems to still have proxifier which was downloaded from git repo, so we would just skip it from reinstalling.

Related Issue

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

• I have read the CONTRIBUTING document.
• I have run the pre-merge tests locally and they pass.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.
• All commits have been signed-off for the Developer Certificate of Origin.

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication