fix(event_source): change the import location of boto3 in CodePipelineJobEvent data class

[darnley]

Issue number: #2352

Summary

Importing boto3 at top level in code_pipeline_job_event.py is affecting performance when import modules that needs aws_lambda_powertools.utilities.data_classes.

Changes

Change the import location of boto3 in code_pipeline_job_event.py to be within function setup_s3_client instead of top level, since this is being used to download an artifact from CodePipeline Job and it is not a common use.

User experience

Decrease of import time when importing modules that uses aws_lambda_powertools.utilities.data_classes, such as ApiGatewayResolver.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• Meet tenets criteria
• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

Is this a breaking change?

RFC issue number:

Checklist:

• Migration process documented
• Implement warnings (if it can live side by side)

Acknowledgment

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

Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

[darnley]

Hey @leandrodamascena!
Since this is a very simple change, do you expect or suggest any new unit tests here to be coded? I think the functionality remains the same.

[leandrodamascena]

Hey @leandrodamascena! Since this is a very simple change, do you expect or suggest any new unit tests here to be coded? I think the functionality remains the same.

Hi @darnley! Yes, we don't need to do anything else you've already done. I just pushed a commit with minor changes because we merged a PR before that and had a conflict.

Thank you so much for sending this PR at lightning speed. 🚀

[leandrodamascena]

APPROVED!