Allow e2e failures in CI

[ryanio]

Description

This PR fixes #3503 by allowing ci jobs to fail by removing continue-on-error.

This PR also tries to fix failures on PRs from forks by removing the git checkout step in e2e.npm.publish.sh since we can use actions/checkout.

More information about the current state and expected outcomes of the ci runs are planned to be documented in #3528.

Type of change

• CI

Checklist:

• I have selected the correct base branch.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• Any dependent changes have been merged and published in downstream modules.
• I ran npm run dtslint with success and extended the tests and types if necessary.
• I ran npm run test:unit with success.
• I ran npm run test:cov and my test cases cover all the lines and branches of the added code.
• I ran npm run build-all and tested the resulting files from dist folder in a browser.
• I have updated the CHANGELOG.md file in the root folder.
• I have tested my code on the live network.

[coveralls]

Coverage remained the same at 89.602% when pulling 0428689 on allow-failures-in-ci into 77d4314 on 1.x.

[cgewecke]

This is great! Thanks for figuring this out. 💯