Update DockerBuildPush.yml

[Jwilson1172]

Description

I'm not 100% sure why the docker buildx didn't work I used the same
PATH context and --file FILE specifications that I use locally

the Build command is:

/usr/bin/docker buildx build \
--tag SECRET \
--iidfile /tmp/docker-build-push-4PJV9W/iidfile \ 
--cache-from type=local,src=/tmp/.buildx-cache \ 
--cache-to type=local,dest=/tmp/.buildx-cache \
--file ./project/Dockerfile \
--push \
./project

the output from the build command is:

unable to prepare context: path "./project" not found

In this PR I try removing the relative path specifier to see if that's the problem.
so the new command is going to be:

/usr/bin/docker buildx build \
--tag SECRET \
--iidfile /tmp/docker-build-push-4PJV9W/iidfile \ 
--cache-from type=local,src=/tmp/.buildx-cache \ 
--cache-to type=local,dest=/tmp/.buildx-cache \
--file project/Dockerfile \
--push \
project

On the next iteration I will rebuild the workflow from scratch if this doesn't work using standard docker build command.
dropping the caching service and builder pool options that come with docker buildx in favor of something that works as expected.

Type of change

• 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

Change Status

• Complete, tested, ready to review and merge
• Complete, but not tested (may need new tests)
• Incomplete/work-in-progress, PR is for discussion/feedback

Has This Been Tested

• Yes
• No
• Not necessary

Checklist

• 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 the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• There are no merge conflicts

[Jwilson1172]

as per docker/setup-buildx-action#29
and https://github.com/docker/setup-buildx-action/tags
the v1 tag uses the v1.0.2 image which may have some problems that have yet to be fully documented.
I may also want to specify the tag as v1.0.1 which was the previous latest stable release of the buildx image.

[lorischl-otter]

Hope this does the trick!