Oci hooks settings extension

[mgsharm]

Issue number:

Closes #3659

Description of changes:

• Creates ock-hooks settings extension and uses it in every variant's settings model.
• Creates settings-oci-hooks RPM package that installs the extension binary.

Testing done:

• Built aws-dev variant with the settings-oci-hooks installed. Launched ec2 instance with the aws-dev variant ami. Connected with the instance via SSM to run apiclient commands.

• Called apiclient to verify the settings-oci-hooks worked as expected.

  [ssm-user@control]$ apiclient get settings.oci-hooks
  {
  "settings": {
  "oci-hooks": {
    "log4j-hotpatch-enabled": false
  }
  }
  }
  [ssm-user@control]$ apiclient set settings.oci-hooks.log4j-hotpatch-enabled=true
  [ssm-user@control]$ apiclient get settings.oci-hooks
  {
  "settings": {
  "oci-hooks": {
    "log4j-hotpatch-enabled": true
  }
  }
  }

• Also tested by building locally.

> cargo run proto1 set --setting-version v1 --value '{"log4j-hotpatch-enabled":true}'
   Compiling settings-extension-oci-hooks v0.1.0 (/Users/mgsharm/bottlerocket/bottlerocket/sources/settings-extensions/oci-hooks)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 2.09s
     Running `/Users/mgsharm/bottlerocket/bottlerocket/sources/target/debug/settings-extension-oci-hooks proto1 set --setting-version v1 --value '{"log4j-hotpatch-enabled":true}'`

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.