…ease

* plugin integration WIP

* add getInitFirebaseResponse type

* satisfy tsconfig.compile.json

* update get-init-firebase-response response format

* isMonospaceEnv

* set access token only in autoAuth

* get monospace daemon port in function

* create `.firebaserc` with authorized project

* don't run setupMonospace if is vs code extension

* return authorized project

* isVSCE from options, return null if no project

* clean up

* use `projectRoot` again, only create rc if ...
... there's a project

* lint friendly assertion

* `/get-init-firebase-response` responses in logger

* handle `userResponse` false

* address nit, replace FIXME with TODO

* depromisify isMonospaceEnv

* remove unnecessary else

* poll every 2 seconds instead of 5

* Increasing timeout on flaking unit tests

* take 2

* Increasing timeouts further

* Found the actual cause - flaky tests were making remote calls and catching 403 errors

* formats

Add emulator support in the VSCode plugin. This is still a prototype version and you may encounter bugs.

* run lifecycle hooks for codebases specified by only

* update changelog

Also fixed an issue where an empty folder creates an issue loading the side panel.

* Fixed a bug in the hosting config for emulators. Also fixed an issue
where an empty folder creates an issue loading the side panel.

* Missed some changes

* Update firebase-vscode/webviews/components/EmulatorPanel.tsx

Co-authored-by: joehan <joehanley@google.com>

---------

Co-authored-by: joehan <joehanley@google.com>

* Update proxyResponse method

* Add proper types to proxyResponse function

* Changelog

* Changelog formatting

* Update CHANGELOG.md

* Update firebase-vscode/package-lock.json

---------

Co-authored-by: joehan <joehanley@google.com>

* Added init flow commands

* change region name

* Enable frameworkstacks api

* Added code review changes

* Revert unwanted changes

* Revert unwanted changes

* Revert unwanted changes

* change according to project id

* Removed unwanted statements related to projectId

* Initial commit to stacks api

* Added more properties to the Stack and Build object

* Added api calls for framework stacks

* Changed naming

* Changed naming

* Review changes

* Removed and used minimal fields

* Moved frameworks api file

* Switched most uses of track to GA4

* Move duration out of params, and improve debug logging slightly

* Release Firestore emulator 1.18.1

* Update CHANGELOG.md

Co-authored-by: joehan <joehanley@google.com>

* Formatting changes in CHANGE.md

* Update CHANGELOG.md

---------

Co-authored-by: Jia You <jiayou@google.com>
Co-authored-by: joehan <joehanley@google.com>
Co-authored-by: christhompsongoogle <106194718+christhompsongoogle@users.noreply.github.com>

…n discovery and emulation (#5985)

When deploying functions that makes use of GCP's usage-based (not resource-based) APIs , such as Vertex AI or ML Vision API, users may see an error like this:


```
// main.py
import vertexai
# Initialize the Vertex AI client
vertexai.init()

$ firebase deploy
Failed to load function definition from source: FirebaseError: Failed to parse build specification

Caused by:
403 Vertex AI API has not been used in project 563584335869 before or it is disabled. 
```

During function discovery, `vertex.init()` makes a call to the Vertex AI with the client credentials associated with Firebase CLI . In the case of usage-based APIs, the call is being made on the Firebase CLI project, not the users project, resulting in the error message like `been used in project 563584335869 before or it is disabled.` (project `563584335869` is the Firebase CLI GCP project).

Similar issue happens when running the function on the emulator.

To workaround the issue, we have to properly override the client project associated with the Vertex AI API call. There are few ways for doing this, and here we choose to leverage `GOOGLE_CLOUD_QUOTA_PROJECT` environment variable to correctly override the quota project to be the user project associated with the Firebase CLI session.

* stash

* commit

* commit

* lint

* fix tests

* const

* Starting on extension.yaml json schema

* finsh extension.yaml schema

* adding events

* add billingrequired

* Adding schemas to vscode plugin too

* reverting new format for firebase-config.json

* Print functions discovery to stdout/error

* More tweaking

* lint fixes

* Use logger instead of console to work with --json

---------

Co-authored-by: Daniel Lee <danielylee@google.com>

Fixes compatibility with latest Next.js

Multi-line table syntax is not supported in GitHub Markdown.

* add internal testing cmd for connecting gh to cloud build repos

* use regex to extract repo slug

* add comments

* add unit tests

* fix tests

* refactoring & allow changing gh app access settings

* refactor & update unit tests

* add comments & change internaltesting name

* rename to composer

* Switched most uses of track to GA4

* Move duration out of params, and improve debug logging slightly

* Improved metrics for extensions

* formats