images deploy / private buckets

[BastLeblanc]

Issue #, if available:

Description of changes:

• removed instructions for deploying from the public buckets
• changed the way we deploy images (now uses a cloudfront distribution serving the image.tar.gz archive)
• upgrade to python 3.12

Description of testing performed to validate your changes (required if pull request includes CloudFormation or source code changes):

• stage.sh + deploy on my account (in eu-west-1 and in us-east-1)
• basic testing of the demo itself

Known issues:

• the internal pipeline is not fixed to accomodate for the buckets being private now
• pandas is updated to 2.x, in some python versions this can cause a long build process (tested on 3.12.2 with no issues)
• This a temporary hotfix to get the developper instructions (stage.sh) working
• https://code.retaildemostore.retail.aws.dev/images.tar.gz is hardcoded for now

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[james-jory]

Do we still need a script that updates the private bucket behind the CloudFront distribution? Minimally, this script would update and copy the images zip and copy the generated CSVs.

[BastLeblanc]

Do we still need a script that updates the private bucket behind the CloudFront distribution? Minimally, this script would update and copy the images zip and copy the generated CSVs.

I propose to keep the existing buildspec.yml and stage to the private bucket behind the code.retaildemostore.retail.aws.dev cloudfront distribution. So we have all the code available on this cloudfront distribution, lambda function, csv, etc. Images are static and only updated if we modify them (not included in the github repo)