[supply] Fixing empty track use case

[androidseb]

The Google Play API returns a different error message body now, and the value of "e.to_s" is now something like this: "notFound: Track not found: alpha". I don't know if the "trackEmpty" case still applies, but I left it there in case.
!!! Please verify and test this before merging !!!
I have not tested this myself and this is just how I assume it should be fixed, maybe it's something completely different.

This is meant to fix a bug that is now happening: the "google_play_track_version_codes" lane will error out if querying for the version codes list of an empty track.

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.

Motivation and Context

Fixes #16159

Description

Testing Steps

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[androidseb]

After a quick search, I noticed someone has reported this as an issue:
#16159

[joshdholtz]

@androidseb Hey! Can you accept the CLA so the we can merge this? 😊

[androidseb]

Hey, yes, sorry, I had been procrastinating on that one, I'll do that today.

[androidseb]

@googlebot I signed it!

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[androidseb]

@joshdholtz we should be good to go now

[joshdholtz]

Looks good! Appreciate the contribution ❤️

[fastlane-bot]

Hey @androidseb 👋

Thank you for your contribution to fastlane and congrats on getting this pull request merged 🎉
The code change now lives in the master branch, however it wasn't released to RubyGems yet.
We usually ship about once a week, and your PR will be included in the next one.

Please let us know if this change requires an immediate release by adding a comment here 👍
We'll notify you once we shipped a new release with your changes 🚀

[etwilliams]

I need this release to push an app update to our beta channel.

[joshdholtz]

@etwilliams This will be getting released today!

[etwilliams]

Fantastic!

[fastlane-bot]

Congratulations! 🎉 This was released as part of fastlane 2.144.0 🚀