[cli-dev-mode/optimizer] omit pageLoadAssetSizeLimit from cache

[spalger]

While working on #95822 I noticed a bug in the @kbn/optimizer cache that I believe @weltenwort had noticed before but we hadn't tracked down, where node scripts/build_kibana_platform_plugins would report that all bundles were cached but they would then be rebuilt when you run yarn start. The problem comes from #93153, where the limitsPath became a parameter passed in via the config. This param isn't passed to the optimizer when it's run via yarn start, and since limits have no bering on the output of the bundles that is fine. To fix this I've excluded the pageLoadAssetSizeLimit from the cache key created for each Bundle which will allow two executions of the @kbn/optimizer which only differ in --limits config to share caches.

To aid in debugging and testing this I also added support for passing the --verbose flag passed to yarn start through to the @kbn/optimizer to enable its verbose logging.

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 41cde6d
• Storybooks Preview

Metrics [docs]

✅ unchanged

History

• 💔 Build #116323 failed afc9df9
• 💔 Build #116292 failed 497f561

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 Backport successful

✅ 7.x / #95856

This backport PR will be merged automatically after passing CI.