Add pass-through `context` argument to allow subfolders

[nwiltsie]

Description

This adds the input variable context, defaulting to ., that is passed straight through to the corresponding input for the docker/build-push-action.

I successfully used this action with this workflow file to create https://github.com/uclahs-cds/tool-Nextflow-action/pkgs/container/nextflow-config-tests.

For good measure I also bumped up the versions of the various sub-actions to get rid of a bunch of deprecation warnings. The https://github.com/jbutcher5/read-yaml action is still throwing warnings but has been archived, so we should either fork and fix it or find a replacement.

Checklist

• [x] This PR does NOT contain PHI or germline genetic data. A repo may need to be deleted if such data is uploaded. Disclosing PHI is a major problem.
• [x] This PR does NOT contain molecular files, compressed files, output files such as images (e.g. .png, .jpeg), .pdf, .RData, .xlsx, .doc, .ppt, or other non-plain-text files. To automatically exclude such files using a .gitignore file, see here for example.
• [x] I have read the code review guidelines and the code review best practice on GitHub check-list.
• [x] I have set up or verified the main branch protection rule following the github standards before opening this pull request.
• [x] The name of the branch is meaningful and well formatted following the standards, using [AD_username (or 5 letters of AD if AD is too long)]-[brief_description_of_branch].
• [x] I have added the major changes included in this pull request to the CHANGELOG.md under the next release version or unreleased, and updated the date.

[yashpatel6]

The https://github.com/jbutcher5/read-yaml action is still throwing warnings but has been archived, so we should either fork and fix it or find a replacement.

Makes sense, I'll convert this to an issue