[AMI] [Feature Request]: Support Bottlerocket on EKS Local cluster on Outposts with EBS

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**
Support Bottlerocket on EKS Local cluster on Outposts with EBS

**Which service(s) is this request for?**
EKS on Outposts

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
Looks like Bottlerocket AMI is supported on EKS on Outposts, but only with "Extended cluster" & "Local cluster on Outposts with EC2 instance store", but not on "Local cluster on Outposts with EBS"

We would like to have Bottlerocket on "Local cluster on Outposts with EBS". Intend behind this request is to use Bottlerocket's in-place upgrade feature to update AMI without re-provisioning EC2 instances.

**Are you currently working around this issue?**
AL2023 AMI is used and AMI refresh requires re-provision of EC2 instances.

**Additional context**
Because of limited hardware resources on Outposts, we are not able to do massive node autoscaling during AMI refresh. Considering to use Bottlerocket's in-place upgrade then restart process to do rolling restart during AMI refresh.

**Attachments**
If you think you might have additional information that you'd like to include via an attachment, please do - we'll take a look. (Remember to remove any personally-identifiable information.)

Start by reviewing the existing EKS on Outposts AMI support matrix and the requirements for Bottlerocket on Local clusters with EBS. Confirm what AWS support or implementation changes are needed, and define done as Bottlerocket being supported for this cluster and storage configuration with the intended in-place upgrade workflow.

Written by the indexing model from the issue text.