create-conda-lock action does not trigger build action

[ateucher]

This is not ideal because it means the most recent image build is not using the most recent conda-lock.

I think I've come across this before where you need some special incantation to get one action to trigger another one. Even though the create-conda-lock action pushes to main, it doesn't trigger the build action, I think by default commits from action bots gets ignored...

[ateucher]

This is still not working...

[ateucher]

Thinking about the workflow on PRs. I think the lockfile should be updated when pushed to a PR, but maybe not necessarily build the image on every push - that seems unnecessary. Especially since we can use the "build your own image" in the Hub to test it out, as long as the lockfile is updated.