configure buildx step to use docker driver

[zeke]

This PR updates the docker buildx configuration to use the docker driver instead of the default docker-container driver.

@one1zero1one's thorough explanation of the issue:

Okay so I figured out the issue, the reason why it goes out to pull the image from a registry - instead of using the locally build one - is the buildx driver, which is docker-container by default - when using setup-cog.

I don't have enough context to understand if the docker-container driver is required (i.e. multi-platform features), but using docker driver in the buildx setup got me over this error and being able to successfully build and push cogs.

I spent many frustrating hours to figure this out, so I'll mention how I debugged - maybe it saves someone else time. I used mxschmitt/action-tmate@v3 action to ssh into my runner, and then used cog debug and cog build --debug to see all the steps (thx to cog developers for exposing this). There I have seen that there are couple of steps, and the last one interprets FROM r8.im/xxx/testas to literally go and pull the image, instead of using the local image. Using the right buildx driver makes it do the right thing.

Resolves these issues:

• Can't build and push image to replicate from github actions workflow. cog#1723 (comment)
• Can't build and push image to replicate cog#1718 (comment)

[zeke]

Tested in this Actions workflow: https://github.com/replicate/sd3-with-actions-workfow/actions/runs/9555684961/job/26339416404

[zeke]

This change landed in https://github.com/replicate/setup-cog/releases/tag/v2.0.2