Cloudformation settings extension

[mgsharm]

Issue number:

Closes #3660

Description of changes:

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

Testing done:

• Built aws-dev variant with the settings-cloudformation 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-cloudformation worked as expected.

[ssm-user@control]$ apiclient set --json '{"settings": {"cloudformation": {"logical-resource-id": "MyEC2Instance", "should-signal":true, "stack-name":"MyStack"}}}'
[ssm-user@control]$ apiclient get settings.cloudformation
{
  "settings": {
    "cloudformation": {
      "logical-resource-id": "MyEC2Instance",
      "should-signal": true,
      "stack-name": "MyStack"
    }
  }
}

• Also tested by building locally.

> cargo run proto1 set --setting-version v1 --value '{"logical-resource-id": "MyEC2Instance", "should-signal":true, "stack-name":"MyStack"}'
   Compiling settings-extension-cloudformation v0.1.0 (/Users/mgsharm/bottlerocket/bottlerocket/sources/settings-extensions/cloudformation)
    Finished `dev` profile [unoptimized + debuginfo] target(s) in 1.28s
     Running `/Users/mgsharm/bottlerocket/bottlerocket/sources/target/debug/settings-extension-cloudformation proto1 set --setting-version v1 --value '{"logical-resource-id": "MyEC2Instance", "should-signal":true, "stack-name":"MyStack"}'`

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.