orchestrator_client-0.6.1 breaks bolt with Ruby 3.1

[smortex]

Describe the Bug

FreeBSD recently switched from Ruby 3.0 to 3.1 as default FreeBSD version. All packages where rebuild with Ruby 3.1, but after updating them, bolt fails to run:

romain@zappy ~ % bolt 
/usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:2287:in `raise_if_conflicts': Unable to activate puppet_forge-4.0.0, because faraday-1.10.3 conflicts with faraday (~> 2.0) (Gem::ConflictError)
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1418:in `activate'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1456:in `block in activate_dependencies'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1438:in `each'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1438:in `activate_dependencies'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1420:in `activate'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1456:in `block in activate_dependencies'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1438:in `each'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1438:in `activate_dependencies'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems/specification.rb:1420:in `activate'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems.rb:282:in `block in activate_bin_path'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems.rb:281:in `synchronize'
	from /usr/local/lib/ruby/site_ruby/3.1/rubygems.rb:281:in `activate_bin_path'
	from /usr/local/bin/bolt:25:in `<main>'

Expected Behavior

Bolt should work as before.

Steps to Reproduce

On FreeBSD:

pkg install bolt

Environment

• Version 0.6.1
• Platform FreeBSD 13.2-RC3

Additional Context

Bolt indirectly depends on two different versions of faraday:

rubygem-bolt-3.26.2
|-> rubygem-r10k-3.15.3_1
|   `-> rubygem-puppet_forge-4.0.0 ([faraday](https://rubygems.org/gems/faraday) ~> 2.0)
|       `-> rubygem-faraday-2.7.4
`-> rubygem-orchestrator_client-0.6.1
    `-> rubygem-faraday1-1.10.3 ([faraday](https://rubygems.org/gems/faraday) ~> 1.4)

Ruby 3.0 seems to cope with this, but 3.1 complains.

Adjusting orchestrator_client-0.6.1.gemspec and changing the version requirement for faraday from ~> 1.4 to ~> 2.0 seems to workaround the issue.

I'll open a PR tomorrow to bump the version requirement.