Fix ASV benchmark configuration issues; don't run benchmarks on non-master fork branches

[kandersolar]

• [ ] Closes #xxxx
• I am familiar with the contributing guidelines
• [ ] Tests added
• [ ] Updates entries in docs/sphinx/source/reference for API changes.
• [ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
• [ ] New code is fully documented. Includes numpydoc compliant docstrings, examples, and comments where necessary.
• Pull request is nearly complete and ready for detailed review.
• Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

This PR fixes several things:

• First, the ASV jobs have been failing since Use pep517/518 build system for modern build isolation #1495 because asv defaults to calling setup.py and wasn't calculating the version string correctly anymore. This affected both our "quick" CI check and the nightly VM job.
• Second, the "quick" CI check wasn't reporting those failures correctly to the github UI, so it showed up as a green check mark instead of a red X.
• Third, address @wholmgren's comment regarding the CI check for forks: CI asv check #1454 (comment)

[AdamRJensen]

@kanderso-nrel I ran the asv locally without issues and reviewed the code changes (to my best efforts). So from my side it looks good, though that might not be saying much

[kandersolar]

Thanks @AdamRJensen, yeah this stuff isn't the easiest to review. The good news is that this isn't really critical infrastructure either :) I think the real proof of review will just be to keep an eye on the asv runs and make sure they're doing the right thing, so I'll go ahead and merge this now.