chore: update to firebase_functions 0.6.0

[brianquinlan]

No description provided.

[gemini-code-assist]

Code Review

This pull request updates the firebase_functions dependency to version 0.6.0 and replaces the fireUp initialization with runFunctions across several Dart quickstart projects. The review feedback identifies that the upgrade to 0.6.0 introduces breaking changes to the onCall handler signature and the removal of CallableResult that have not been addressed in the code. Furthermore, it is recommended to use await runFunctions in the main entry points to ensure proper lifecycle management of the server.

[gemini-code-assist]

The update to firebase_functions 0.6.0 introduces breaking changes that are not fully addressed in the function handlers:

1. onCall Signature: The handler now takes a single CallableRequest argument. The response object is now a property of the request object. You must update line 52 to (request) async { and line 76 to await request.response.sendChunk(result);.
2. CallableResult Removal: This class has been removed in 0.6.0. You should return the result directly (e.g., return await Future.wait(allRequests); on line 86).
3. Async Main: It is recommended to await runFunctions to ensure the entry point correctly handles the server's lifecycle.

Suggested change

	void main() {
	runFunctions((firebase) {
	void main() async {
	await runFunctions((firebase) {

[gemini-code-assist]

The update to firebase_functions 0.6.0 requires updates to the onCall handler signature and return type:

1. onCall Signature: The handler on line 25 should be updated to take only one argument: (request) async {. The response argument is no longer passed separately.
2. CallableResult Removal: The CallableResult wrapper on line 60 should be removed, and the map should be returned directly. Remember to also remove the closing parenthesis on line 65.
3. Async Main: Consider using await runFunctions for better lifecycle management.

Suggested change

	void main() {
	runFunctions((firebase) {
	void main() async {
	await runFunctions((firebase) {

[gemini-code-assist]

It is recommended to await runFunctions to ensure the entry point handles the server's future correctly, even if the event loop keeps the process alive.

Suggested change

	void main() {
	runFunctions((firebase) {
	void main() async {
	await runFunctions((firebase) {

[gemini-code-assist]

It is recommended to await runFunctions to ensure the entry point handles the server's future correctly.

Suggested change

	void main() {
	runFunctions((firebase) {
	void main() async {
	await runFunctions((firebase) {