[@types/chromecast-caf-receiver] cannot be used with TS verbatimModuleSyntax or isolatedModules enabled #74025

My apologies for breaking things in #73421. The original addition of enums in #40166 was wrong, but so was my change to const enum. I have #75811 up for review now, which I hope will satisfy both my usage and everyone else's.

CAF's enums are plain objects on the global cast namespace, with literal string and number values. So my new PR declares each one as a const object with readonly literal properties, plus a same-named union type of its values. This should work for everyone, but it's a structural change and there might be some minor adjustments required, depending on how the dependent app is written. So my PR also bumps the major version of the types. (The type versions are already not connected to the library versions.)

Tagging:

• @3flex, who opened the discussion
• @friday, who first raised it on Move Chromecast SDK enums to const enum #73421
• @lkinasiewicz, who reported the esbuild/Vite breakage
• @jbishop-cbs, who wrote the revert, and wrote its regression-guard tests, which the new PR keeps