[BLD]: use blacksmith pull-through container image cache for Tilt cluster

[codetheweb]

Description of changes

We have been frequently seeing image pulls fail when starting Tilt in CI due to rate limiting/network issues. This configures the kind cluster to use blacksmith's provided pull-through image cache which should resolve these issues.

Test plan

How are these changes tested?

I changed the cache mirror port to be incorrect and observed that workflows immediately failed.

Documentation Changes

Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs section?

n/a

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[propel-code-bot]

Configure Blacksmith Pull-through Image Cache for Tilt CI Cluster

This PR updates the GitHub Actions workflow for starting Tilt services in CI to address frequent Docker image pull failures caused by rate limiting or network issues. It replaces the direct kind cluster configuration with the use of the Blacksmith pull-through container image cache and switches to the helm/kind-action for cluster setup, ensuring more reliable image pulls.

Key Changes:
• Upgraded Tilt version from 0.33.3 to 0.34.2 in the workflow.
• Removed ctlptl installation and direct kind setup in favor of helm/kind-action@v1.
• Configured kind to use an internal registry and enabled image delete.
• Added a step that updates kind nodes to use the Blacksmith image cache as a Docker registry mirror.
• Tested failure scenarios by setting an incorrect mirror port (reverted in final commit).

Affected Areas:
• GitHub Actions workflow (.github/actions/tilt/action.yaml)
• CI infrastructure setup for Tilt/kind clusters

This summary was automatically generated by @propel-code-bot

[HammadB]

We should update hosted/ as well. Although IIRC it may use this