feat: Add support for configurable REGISTRY_URL to download Databricks CLI from custom registrie

[GezimSejdiu]

Description:

This pull request introduces support for specifying a custom REGISTRY_URL in the GitHub Action to download the Databricks CLI from either the default GitHub registry or a private/custom registry (e.g., Artifactory or another mirror).

Key Changes:

1. New registry_url Input:

   • Added a new input parameter registry_url to the GitHub Action.
   • This parameter allows users to define a custom registry URL for downloading the Databricks CLI. If no value is provided, it defaults to https://github.com.

   Example Usage:

      - uses: databricks/setup-cli@main
        with:
           version: 0.221.1
           registry_url: 'https://your-private-registry.com/artifactory'

2. Default to GitHub:

   • If no registry_url is passed, the GitHub Action will automatically use https://github.com for downloading the Databricks CLI.

3. Updated Bash Script (setup_release.sh):

   • The script now dynamically uses the REGISTRY_URL input to download the Databricks CLI. If the REGISTRY_URL is not provided, the download will default to GitHub.

4. Backward Compatibility:

   • This change is fully backward-compatible. If no custom registry_url is specified, the GitHub Action will behave exactly as before, pulling the Databricks CLI directly from GitHub.

---

Why This Change is Important:

• Flexibility: This enhancement allows users to download the Databricks CLI from private mirrors or registries, which can be useful in environments where access to external resources like GitHub is restricted.

• Default Behavior Intact: The default behavior remains the same, ensuring that users who do not require a custom registry will continue downloading from GitHub without any additional configuration.

Let me know if you'd like any adjustments or if there are specific points to elaborate further!