removing activesupport direct dependency

[johnmccrae]

Description

Acitvesupport is being a nightmare to manage. It has been removed from Chef Zero and Chef 19. We are trying to get rid of it across the board. In removing it from oc-chef-pedant we also noted a dependency on the chef-18 chef client. It was added solely to extract the chef version number. Why? That brought in an incredible amount of overhead and dependencies that we had no need for. This PR updates the KNIFE_VERSION constant to a known shipping chef-client version. The code had previously hard-coded a chef version in the gemfile so we just moved that version over to the request.rb file. Removing activesupport also had an effect on various other files since the code was actively using that gem. This was going to create a huge problem in chef-19, and chef-zero since they do NOT use activesupport. We updated things to replace the features that activesupport was providing. Finally, we also added a spec_helper and a readme so that users could test various spec files locally. Normally, you'd need a whole chef-server to run spec tests against but with the spec_helper you can bypass that for some of the tests. Anything that makes an HTTP request is going to fail but this helps.

Issues Resolved

[List any existing issues this PR resolves, or any Discourse or
StackOverflow discussions that are relevant]

Check List

• New functionality includes tests
• All buildkite tests pass
• Full omnibus build and tests in buildkite pass
• All commits have been signed-off for the Developer Certificate of Origin. See https://github.com/chef/chef/blob/main/CONTRIBUTING.md#developer-certification-of-origin-dco
• PR title is a worthy inclusion in the CHANGELOG

[netlify]

👷 Deploy Preview for chef-server processing.

Name	Link
🔨 Latest commit	002e836
🔍 Latest deploy log	https://app.netlify.com/projects/chef-server/deploys/69094336ba04990008cc14a1

[rahulgoel1]

I talked to Marc Paradise about this and he advised me to do a full 'bundle update' on oc-chef-pedant, although that has nothing to do with most of the failures. However, in doing that, I encountered an error with unf_ext saying version 0.0.8.2 was not compatible with Ruby 3.4. That IS a problem given that we are all headed to Ruby 3.4 so I am starting work on updating that. Can someone take a look at the chef-server specific failures though?

@kalroy can someone from server team help out with the server specific failures? This is blocking the chef 19 RC3.

[johnmccrae]

Updating this - I have resolved everything but the server hab package issues. Can someone take a look? Also, we're putting the issue of support for Ruby 3.4 into another PR later.

[sreepuramsudheer]

Adhoc : https://buildkite.com/chef/chef-chef-server-main-omnibus-adhoc/builds/7797

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[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