Surface worker requests in performance diagnostics

`response-compression` and `uses-optimized-images` needed to explicitly ignore worker requests in https://github.com/GoogleChrome/lighthouse/pull/14212 to maintain their same behavior. That being said, we could analyze worker requests in these audits if we wanted to.

The justification for ignoring OOPIF is that developers don't have as much control over the requests in third parties (https://github.com/GoogleChrome/lighthouse/pull/7640#issuecomment-477856251). However, web workers can be first party so it's reasonable to expect developers to optimize the requests coming from first party web workers.

Previous discussions
https://github.com/GoogleChrome/lighthouse/pull/7640
https://github.com/GoogleChrome/lighthouse/pull/7795

Start by reviewing the referenced pull requests 14212, 7640, and 7795, then locate the response-compression and uses-optimized-images audits they discuss. Determine how worker requests are currently excluded and define the expected treatment for first-party web workers. Done means the audits analyze eligible worker requests without changing their existing behavior for other request types.

Written by the indexing model from the issue text.