Add dcp_trigger_build with GitHub links and log tailing

[alexrichey]

Never Futz with the GHA build dataset dialogue ever again!

• Add direct GitHub Actions run URL after dispatching workflow
• Automatically tail logs by default for immediate feedback
• Add --no-tail flag to skip log tailing when desired

Usage examples:

# From product directory (uses DATASET from direnv) 
cd products/pluto && dcp_trigger_build

# Explicit dataset
dcp_trigger_build pluto

# With custom recipe and build note
dcp_trigger_build pluto my_recipe "test build"

# Skip log tailing 
dcp_trigger_build pluto --no-tail

Note: When in a products/* directory with direnv enabled, the DATASET environment variable is automatically set, so you can run the command without any arguments.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 73.69%. Comparing base (19de2d5) to head (15de73f).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[damonmcc]

nice!

the github CLI seems simple enough to do this via bash. in general though, fair to say we still prefer python over bash for custom scripts? we don't get the bonus of adding those to our path though like we do with bash scripts in bash/bin/

[alexrichey]

nice!

the github CLI seems simple enough to do this via bash. in general though, fair to say we still prefer python over bash for custom scripts? we don't get the bonus of adding those to our path though like we do with bash scripts in bash/bin/

@damonmcc It's mostly about auth, and that the CLI enables you to do the auth flow and store the results. Whereas with Python I suppose we'd have to store some creds in the .env or something.