Updating Gem versions - specifically updating Chef for omnibus

[johnmccrae]

Signed-off-by: John john.mccrae@progress.com

Updating the chef version in Omnibus.

Description

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.

[tpowell-progress]

🤔 it looks clean enough, but can we redo this without the big merge commit up front?

[neha-p6]

Do we have an adhoc build testing this? If not, can we run an adhoc build please?

[jaymzh]

Can we get a description here of all the things we're changing and why? We spent about 10 minutes in the PR Review meeting digging around in the rest-client/rest-client PRs and this one and still can't quite piece this all together enough to give a meaningful review. Thanks!

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[Stromweld]

LGTM

[tpowell-progress]

Ok, much cleaner. Let’s make sure to squash and merge at the end

[PrajaktaPurohit]

Could we paste the passing adhoc builds before merging?

[johnmccrae]

Here's the relevant AdHoc build - everything passes except the enterprise linux pieces which are failing for everything right now
https://buildkite.com/chef/chef-chef-main-omnibus-adhoc/builds/1760