Fix Shaka Player version numbers

[joeyparrish]

This corrects the release numbers in Shaka Player v2.0.3, v2.0.4, and
v2.1.3.

Closes shaka-project/shaka-player#869

Essential checklist

• I'm the author of this library
  • I would like to add link to the page of this library on CDNJS on website / readme
• This lib was not found on cdnjs repo
• No already exist / duplicated issue and PR
• The lib has notable popularity
  • More than 100 [Stars / Watchers / Forks] on [GitHub / Bitbucket]
  • More than 500 downloads stats per month on npm registry
• Project has public repository on famous online hosting platform (or been hosted on npm)

Git commit checklist

• The first line of commit message is less then 50 chars, be clean and clear, easy to understand.
• The parent of the commit(s) in the PR is not old than 3 days.
• Pull request is sending from a non-master branch with meaningful name.
• Separate unrelated changes into different commits.
• Use rebase to squash/fixup dummy/unnecessary commits into only one commit.
• Close corresponding issue in commit message (can't, the issue is in another repo)
• Mention related issue(s), people in commit message, comment.

[PeterBot]

@joeyparrish congratulations! 0291219 CI test passed! ✅
Please wait for the further review from the maintainers!

For the details 📃, please take a look at ➡️ https://ci.cdnjs.com/cdnjs/cdnjs/9111, thank you 😀

[PeterDaveHello]

@joeyparrish I'm afraid that this can't be done as we enabled SRI already and this change would make the current users' website broken, if it's only about version number, maybe we don't really need to touch it?

[joeyparrish]

I'm not familiar with SRI. What would break if we merged this PR?

[PeterDaveHello]

@joeyparrish Just think SRI is kind of checksum, the modified files would have different hashes so that the old would not work.

Ref: https://www.w3.org/TR/SRI, https://developer.mozilla.org/en-US/docs/Web/Security/Subresource_Integrity

[joeyparrish]

I see. So based on that MDN article, if we change these files that have already gone out, they may appear to be malicious changes. Do I understand you correctly?

[PeterDaveHello]

@joeyparrish yes, that's why we shouldn't touch the published files.

[joeyparrish]

Okay, understood. I'll close this now. Thank you for your feedback.

[PeterDaveHello]

@joeyparrish Thanks.