fix: remove test-kitchen dependency

[Stromweld]

Description

Allows support for Chef's new chef-test-kitchen-enterprise

Type of Change

Our release process assumes you are using Conventional Commit messages.

The most important prefixes you should have in mind are:

• _fix_: which represents bug fixes, and correlates to a SemVer patch.
• _feat_: which represents a new feature, and correlates to a SemVer minor.
• _feat!_:, or fix!:, refactor!:, etc., which represent a breaking change (indicated by the !) and will result in a major version change.

If you have not included a conventional commit message this can be fixed on merge.

Check List

• New functionality includes tests
• All tests pass
• Commit message includes a Conventional Commit Message

[damacus]

Converting to draft until we can discuss the implications of this as a group.

[ramereth]

Could this maybe be worked around on your environment with an environment variable? Perhaps something like this:

unless ENV['CHEF_TEST_KITCHEN_ENTERPRISE']
  gem.add_dependency "test-kitchen", ">= 1.4", "< 4"
end

I'm not sure if this will work but it's a thought. By default I'd like to keep this dependency if possible.

Will the other gem be published on rubygems.org or only in a private repo?

[Stromweld]

didn't think of that. Then could do if statement ENV true gem ctke else tk. Does that mean though that whever the vagrant gem is used with ctke that they'd need to set that attribute to true or only when doing something like gem or bundle install?