#1839 Remove the set-python action from the lambda-functions.yml workflow

[kalbfled]

Description

These changes remove the set-python action from the lambda-functions.yml workflow, which is a legacy step from when we used to bundle dependencies with lambda code upon deployment. (We use layers now.)

issue #1839

Type of change

Please check the relevant option(s).

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update
• Documentation changes only
• other

How Has This Been Tested?

How has this been tested? (e.g. Unit tests, Tested locally, Tested as a GitHub action, Depoyed to dev, etc)
Please provide relevant information and / or links to demonstrate the functionality or fix. (e.g. screenshots, link to deployment, regression test results, etc)

I deployed the VA Profile Opt-in/out lambda to Dev from the master branch using this PR's branch for the workflow. Then I verified in the Lambda console that everything is as expected. I am satisfied that removing the set-python step has no effect on the deployment.

Checklist

• I have assigned myself to this PR
• PR has an appropriate title: #9999 - What the thing does
• PR has a detailed description, including links to specific documentation
• I have added the appropriate labels to the PR.
• I did not remove any parts of the template, such as checkboxes even if they are not used
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to any documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• I have ensured the latest master is merged into my branch and all checks are green prior to review
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• The ticket is now moved into the DEV test column

[kalbfled]

This PR should not be merged before Monday (7/15). Cris has a new plan. Green light.