chore: bump python modules to latest supported version

[qdzlug]

Describe the bug We need to bump our python modules to keep pace with the development of the Python SDK from Pulumi. The key areas that need to be updated are:

1. Modules defined in Pipfile in the main pulumi/python directory.
2. Modules defined in setup.py for the KIC Utilities.

To build the Pipfile.lock you can simply change the setup_venv.sh script to use update instead of sync on it's calls to pipenv. The you can revert the shell script and check in those files.

Currently, attempting to bump any of the Pulumi SDK related modules results in issues logging into the registry; this happens every time with Digital Ocean but has not be attempted with any other providers.

Errors are of the format:

    pulumi:pulumi:Stack kic-image-push-marado66 running /home/jschmidt/data/repos/kic-reference-architectures/pulumi/python/utility/kic-image-push/./registries/base_registry.py:52: RuntimeWarning: coroutine 'login_to_registry' was never awaited
    pulumi:pulumi:Stack kic-image-push-marado66 running   docker.login_to_registry(registry=registry, log_resource=None)
    pulumi:pulumi:Stack kic-image-push-marado66 running RuntimeWarning: Enable tracemalloc to get the object allocation traceback
    pulumi:pulumi:Stack kic-image-push-marado66 running Logged into container registry: https://registry.digitalocean.com
    pulumi:pulumi:Stack kic-image-push-marado66 running error: Program failed with an unhandled exception:
@ Updating....
    pulumi:pulumi:Stack kic-image-push-marado66 **failed** 1 error; 4 messages

So it does look to be something in our utility lib, but not sure what.

To Reproduce Steps to reproduce the behavior:

1. Bump modules.
2. Build venv.
3. Run on DO
4. Watch it blow up at the login to registry stage.

Expected behavior Should work.

Your environment

• n/a

Additional context None