Add bundle size limits and tracking to Github CLI

[arafatkatze]

Add size limit enforcement and historical tracking for extension bundles to prevent unexpected size increases. This helps maintain performance and download speeds for users.
Part of the linear issue for Cody Performance

The purpose of this PR is to have bundle sizing measurements for both the extension and the webview. After having them, integrate them into the CI. If you were to add a dependency that increases the bundle size by a lot, it will fail the CI, therefore you have to be cautious about making reckless changes. If you really have to do it, making changes in the CI would force you to make potential changes with extension bloating carefully. NOTE the limit is set to 10% extra so its unlikely you will hit that limit unless you do some really reckless changes.

NOTE: This PR also puts the size of the bundle in bigquery on every release

This PR also tracks the bundle sizes on every pre-release along with the date so we have a record of the time when small changes happened and we can then use the bigquery table to see how the bundle sizes evolved.

Test plan

• Actually run the Github Actions CI
  The failure mode looks like this and you see this failure mode on the build step so when you do a build and it makes very large bundle then the build fails and you have to talk to team cody core to get permission from Grace/dom before making big changes but for small bundle changes this will pass.

• How did I check if this works with the release github actions?
  Since I couldn't actually run the release github action as that would make the release I decided to make a close approximation in another github action which would entail getting the release version and then making a bigquery request to update a row in the table to mark the date and the sizes of the bundles

This is the response of my fake requests

This is the workflow file and this is the run.

Changelog