Bicep commands fails due to error in version check

**Bicep version**
```
> az bicep version
Bicep CLI version 0.38.33 (6bb5d5f859)
```

**Describe the bug**
Running a bicep command that should only affect local resources, such as build, decompile, lint, etc. fails when `downloads.bicep.azure.com` is unavailable.

```
> az bicep build-params -f ./parameters/main.bicepparam
Error while attempting to retrieve the latest Bicep version: HTTPSConnectionPool(host='downloads.bicep.azure.com', port=443): Max retries exceeded with url: /releases/latest (Caused by NameResolutionError(": Failed to resolve 'downloads.bicep.azure.com' ([Errno -2] Name or service not known)")).
```

**To Reproduce**
Block the host locally by changing the `/etc/hosts` configuration to send this domain to a invalid location, or to a location that does not answer. Run any "local" bicep command.

**Additional context**
Due to the Azure Front Door outage on October 29th 2025, local commands were affected. Some colleagues reported very long execution time before failure, as it seemed like the Http timeout configuration was very long.

Reproduce the failure by blocking downloads.bicep.azure.com, then trace the version check used by a local command such as `az bicep build-params -f ./parameters/main.bicepparam`. Done means local Bicep commands work when the host is unavailable and the failed network request does not cause an excessively long wait.

Written by the indexing model from the issue text.