fix: use guid to ensure uniqueness of track setting options

[mister-ben]

The fix for the previous issue with the new text track settings introduced that ids would be re-used across players as there was no prefix for the settings that don't have a <label> for their <select>.

This change uses a generated guid for items without that label.
Fixes #8761

Requirements Checklist

• Feature implemented / Bug fixed
• If necessary, more likely in a feature request than a bug fix
  • Change has been verified in an actual browser (Chrome, Firefox, IE)
  • Unit Tests updated or fixed
  • Docs/guides updated
  • Example created (starter template on JSBin)
  • Has no DOM changes which impact accessiblilty or trigger warnings (e.g. Chrome issues tab)
  • Has no changes to JSDoc which cause npm run docs:api to error
• Reviewed by Two Core Contributors

[mister-ben]

Unrelated to issue, resolving jsdoc warnings from lint.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.62%. Comparing base (fc1f7a6) to head (cb4c2ef).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #8762      +/-   ##
==========================================
+ Coverage   83.01%   83.62%   +0.61%     
==========================================
  Files         119      119              
  Lines        7993     7993              
  Branches     1922     1923       +1     
==========================================
+ Hits         6635     6684      +49     
+ Misses       1358     1309      -49     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.