Add personalised lambda using dynamic fetcher lambda

[Divs-B]

What does this change?

We have request for personalised container to be available for the Feast users.
The container will present the recipes that are accessed by the user in last 10 days(the number of days is fixed to start with but can be changed later).

Recently we had similar work done in dynamic container so using that as a base to get this work bit fast forward.
So I cloned down the dynamic-fronts-fetcher lambda and made the changes according to personalised container requirement.
The plan is to refactor by extracting common logic already done in dynamic lambda to avoid the duplication later.

Need to get this deploy to get it on Infra, which will help in getting service account, role registered for this lambda to get used by Data tech team. they need for GCS bucket creation required for personalised container.

Other information regarding the tech document and diagram will be added eventually.

How to test

Deploy on CODE and observe the feast account

How can we measure success?

Feast aws account should be getting personalised lambda and other information registered.

Have we considered potential risks?

Images

Accessibility

• Tested with screen reader
• Navigable with keyboard
• Colour contrast passed
• The change doesn't use only colour to convey meaning

[github-actions]

Deploy build 862 of Feast::recipes-backend to CODE

All deployment options

• Deploy build 862 of Feast::recipes-backend to CODE
• Deploy parts of build 862 to CODE by previewing it first
• What's on CODE right now?

---

From guardian/actions-riff-raff.

[Divs-B]

Closing this. We have got PR #143 in place which don't remove the need of this lambda.