feat: support more key system error detail

[JackPu]

This PR will...

We will trigger more DRM-related errors to help the app collect that information.

Why is this Pull Request needed?

Even though we covered most devices and browsers. But there are still some devices that can not run it in an expected way. And they are not easy to debug with real ones. So we want to support more detailed error information to trigger for us to report.

Are there any points in the code the reviewer needs to double check?

Resolves issues:

Checklist

• changes have been done against master branch, and PR does not conflict
• new unit / functional tests have been added (whenever applicable)
• API or design changes are documented in API.md

[JackPu]

@robwalch Hi, do I need to add some unit tests for this? Or do you have your own ideas about the implementation?

[robwalch]

@robwalch Hi, do I need to add some unit tests for this? Or do you have your own ideas about the implementation?

Take a look at tests/unit/controller/eme-controller.ts. I don't know if we have mocks for producing and cover similar errors so it's OK if you don't add new tests for these non-fatal errors.

You need to fix the build (https://github.com/video-dev/hls.js/actions/runs/11626288545/job/32377670037?pr=6807) before we can merge. Running npm run sanity-check will run sub-task npm run docs which will add the missing API changes to "api-extractor/report/hls.js.api.md" you're changing with this PR (new ErrorDetails enums).

[JackPu]

Thanks a lot. I will update it. I don't see any reply with the PR. I am not sure if I need to continue with it.