core(config): import LH types in exported configs

[lawrence3699]

Summary

• fixes the generated declaration files for exported configs that currently emit LH.Config without importing ../../types/lh.js
• reproduces lr-mobile-config.d.ts breaks TS builds: Cannot find namespace 'LH' #16503 and the same missing-import problem on the other exported config entry points in core/config/
• aligns these config modules with the existing pattern already used by configs like default-config.js and desktop-config.js

Related Issues/PRs

• Fixes lr-mobile-config.d.ts breaks TS builds: Cannot find namespace 'LH' #16503

Failing scenario before this change:

• a strict TypeScript project importing lighthouse/core/config/lr-mobile-config.js failed with TS2503: Cannot find namespace 'LH'
• the generated .d.ts for the affected config exports declared LH.Config without importing ../../types/lh.js

After this change:

• the emitted declarations import ../../types/lh.js, so those config entry points type-check correctly for external consumers

Validation:

• yarn type-check
• strict external consumer tsc against the built repo tree importing the affected core/config/*.js entry points
• yarn build-pack
• strict external consumer tsc against the packed dist/lighthouse.tgz importing lighthouse/core/config/lr-mobile-config.js, lighthouse/core/config/lr-desktop-config.js, and lighthouse/core/config/perf-config.js

[google-cla]

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

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[paulirish]

Nice. seems good.

can you sign the CLA?

[paulirish]

Nice. seems good.

can you sign the CLA?

@lawrence3699 plz :)