fix: prune botocore service models from lambda dockerfile

[kafitzgerald]

Summary

Following the approach from #151 prunes botocore service models from the lambda Dockerfile. Needed for #184 which is currently just over the size limit for the CDK stack.

Testing

None

PR checks

• Standard CI runs automatically on each push.
• To run the CDK synth check, add the run-cdk-checks label to this PR.
• If you push more commits after that run completes, remove and re-add the label to run it again.
• To trigger a dev deployment, add the deploy-dev label. It smoke-tests tiles from the native MUR, virtual MUR, and virtual NLDAS Icechunk stores after deployment.

[maxrjones]

I wonder if this is a more comprehensive pruning that we could use:

https://github.com/developmentseed/titiler-cmr/blob/316642b7191f6f8a30fc76e24aeebc34e6d13a9a/infrastructure/aws/lambda/Dockerfile#L170-L184

It might be worth testing out

[kafitzgerald]

I wonder if this is a more comprehensive pruning that we could use:

https://github.com/developmentseed/titiler-cmr/blob/316642b7191f6f8a30fc76e24aeebc34e6d13a9a/infrastructure/aws/lambda/Dockerfile#L170-L184

It looks like we already have most of this with the exceptions of fully removing boto3 and botocore, but those seem to be needed here (unless the comments are incorrect).

[maxrjones]

I wonder if this is a more comprehensive pruning that we could use:
developmentseed/titiler-cmr@316642b/infrastructure/aws/lambda/Dockerfile#L170-L184

It looks like we already have most of this with the exceptions of fully removing boto3 and botocore, but those seem to be needed here (unless the comments are incorrect).

oh gosh yeah, sorry about that. I should've looked more at the surrounding code.