CASMINST-6602 - enable dkms by default.

[dlaine-hpe]

Summary and Scope

There was a request by cos to have the require-dkms default to 'true' instead of 'false' like it originally released. This changes the defaults and had to modify the logic a little bit to get it right for integrating with the 'require_dkms' flag in the recipe records.

Issues and Related PRs

• Resolves CASMINST-6602

Testing

Tested on:

• Mug

Test description:

I deployed the new helm chart to ensure the correct default value is applied to the ims-config settings. I then tested each combination of global and per record settings to make sure the correct use of dkms was determined in each scenario.

• Were the install/upgrade-based validation checks/tests run (goss tests/install-validation doc)? N
• Were continuous integration tests run? If not, why? N
• Was upgrade tested? If not, why? Y
• Was downgrade tested? If not, why? Y
• Were new tests (or test issues/Jiras) created for this change? N

Risks and Mitigations

Fairly low risk and there are workarounds if the default settings are not what the user wants.

Pull Request Checklist

• Version number(s) incremented, if applicable
• Copyrights updated
• License file intact
• Target branch correct
• CHANGELOG.md updated
• Testing is appropriate and complete, if applicable