2.0.0 orb is broken and should be flagged more obviously

[bxjw]

Orb Version
2.0.0

Describe the bug
CircleCI started throwing this error even though we did not upgrade to 2.0.1. It fixed itself once we upgraded the orb, but there was no indication anywhere that the upgrade was a breaking change on previous orb versions.

bash: line 1: syntax error near unexpected token `newline'
bash: line 1: `<?xml version='1.0' encoding='utf-8' ?>'

To Reproduce
Have orb 2.0.0 as before and run the workflow to completion.

Expected behavior
It should not break, or people should be appropriately warned to upgrade.

[efinlay24]

Our engineering teams have encountered the same problem today.

It seems to be a problem with the hosting service that orb attempts to retrieve the install.sh script from:
https://sls-standalone-sv-1300963013.cos.na-siliconvalley.myqcloud.com/install.sh

The script itself isn't available, and when I visit that URL, I get the following XML formatted error instead:

<Error>
<Code>UnavailableForLegalReasons</Code>
<Message>Due to your account is arrears, it is unavailable until you recharge.</Message>
<Resource>/install.sh</Resource>
<RequestId>NjM5YzdmNjZfZmFlYzVlMGJfZmM5OV8yY2IzNTZl</RequestId>
<TraceId>OGVmYzZiMmQzYjA2OWNhODk0NTRkMTBiOWVmMDAxODc0OWRkZjk0ZDM1NmI1M2E2MTRlY2MzZDhmNmI5MWI1OTVhZmNjOGRhMDFhODRkMDI4YmJmYmQyZDI5OGM4MzJlZDUwMzU1YThlNzViMjRlZDc1YmM4YzUzMDhiMzVlZTM=</TraceId>
</Error>

This is causing the orb to fail, as bash cannot execute that XML file.

We're currently in the process of upgrading our projects to use the fixed 2.0.1 version of the orb which will download the script from a working mirror instead.

[innomatics]

We got another error: Error: The environment variable SERVERLESS_ACCESS_KEY is empty which was resolved by upgrading to 2.0.1 (we don't use a key, and the job worked previously).