L2 Construct for AWS Elemental Inference

## Description

L2 Constructs design for AWS Elemental Inference - this comprises of 2 main resources: Feed and Dictionary

## Roles

| Role | User
|---------------------|------------------------------
| Proposed by | @jamiepmullan
| Author(s) | @jamiepmullan
| API Bar Raiser | (TBC)
| Stakeholders | (TBC)

> See [RFC Process](https://github.com/aws/aws-cdk-rfcs#rfc-process) for details

## Workflow

- [x] Tracking issue created (label: `status/proposed`)
- [ ] API bar raiser assigned (ping us at [#aws-cdk-rfcs](https://cdk-dev.slack.com/archives/C025ZFGMUCD) if needed)
- [ ] Kick off meeting
- [ ] RFC pull request submitted (label: `status/review`)
- [ ] Community reach out (via Slack and/or Twitter)
- [ ] API signed-off (label `status/api-approved` applied to pull request)
- [ ] Final comments period (label: `status/final-comments-period`)
- [ ] Approved and merged (label: `status/approved`)
- [ ] Execution plan submitted (label: `status/planning`)
- [ ] Plan approved and merged (label: `status/implementing`)
- [ ] Implementation complete (label: `status/done`)

---

> Author is responsible to progress the RFC according to this checklist, and
apply the relevant labels to this issue so that the RFC table in README gets
updated.

Start with the linked RFC Process and the tracking issue checklist. The proposal covers two resources, Feed and Dictionary, but no API details or implementation files are provided. Progress requires defining the L2 design, assigning an API bar raiser, submitting the RFC for review, and completing the listed approval and implementation stages.

Written by the indexing model from the issue text.