fix: wait for lambda function state updates

[jsetton]

Issue #, if available:

Fixes: #415

Description of changes:

This change adds waiting for Lambda function state updates support which is now required per this blog post. The lambda-deployer workflow will now wait after each Lambda function operations (create, add event permission, update code and update configuration) while the function state and last update status are pending/in progress. Once these properties are available, the deployment workflow will only continue if the function state is Active and the last update status is Successful.

A fix for the Windows test integration is also included. The Windows image now runs Python 3.10 which is breaking the Python build flow as it is currently only expecting single digit minor version.

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

[sam-goodwin]

Thanks so much for donating your time to fix and test this. One last question: have you tested this change with a lambda that is opted in to States and on that is not?

[jsetton]

One last question: have you tested this change with a lambda that is opted in to States and on that is not?

I tested with the default behavior which is opt-in at this point. Does the opt-out workaround still work? If so, I can give a try when I get back in front of a computer.

[jsetton]

So the opt-out workaround still works. I was able to confirm that this fix works with the previous (opt-out) and the default (opt-in) behaviors.

[jsetton]

@sam-goodwin any plan to merge this PR and create a new release?

[Shreyas-vgr]

Thanks @jsetton for the PR, I will merge this and release a new CLI version asap.