az bicep version check should not block on failure

**Related command**
`az bicep *`
`az deployment *` (with a bicep template file)

**Is your feature request related to a problem? Please describe.**
the `az` commands that use bicep, check for a newer version of bicep before initiating the command. If that version check fails for some reason (e.g. 4xx) the command stops and the user is blocked from using any command that involves bicep in the cli

**Describe the solution you'd like**
ignore failures that occur during the bicep version check and continue running the user's command

**Describe alternatives you've considered**
the user can modify the json file that has a timestamp for a version check to a future date and that will unblock, but for users running pipelines this is not always trivial.

**Additional context**
We are working on changes that will make the check more resilient, but even with that -- in the event of a failure, we should not block the user's command.