Dagger GitHub action

[coral spear]

@true hatch I agree. We could:

• delist the old action from GH Marketplace but leave repo in place
• indicate that the old action is deprecated
• copy the repo to a new one called dagger-cue-for-github or similar
• use dagger-cue https://github.com/dagger/dagger-for-github/issues/75 in new one
• optionally put new one in GH Marketplace, but prob leave out
• investigate idea of a GH action for running scripts that use the new language SDKs. We're looking into that right now. cc @rare iron

made issue here: https://github.com/dagger/dagger/issues/3964

[iron sparrow]

One concern I'd have about this is breaking workflows for people who are currently using it.

[coral spear]

yep. by leaving it in place in github, but delisting it from GH Marketplace, it would continue to work for existing folks.