OAI being used instead of OAC for access control of S3andCloudfront hosting

### Amplify CLI Version

10.5.1

### Question

We are using S3andCloudfront hosting to host our sites.
We use amplify env add, amplify publish commands to add new sites.
Recently we noticed that it is using the legacy OAI (Origin Access Identity)
rather than the recommended OAC (Origin Access Control).

We could not find any way to tell amplify to use OAC instead of OAI.
How can we do this?

Also, can we use the same OAC/OAI for multiple sites?
amplify publish creates a new OAI for each new env (site),
so the number of OAI reached 100 and we cannot create any more site
due to AWS quota. Hence we ask this question.