[PROD] GET templates v2 API needs to get updated to not include default values for connection string properties

[etheodoridou]

Create type v1 or v2: v2
App kind (linux/windows, code/container): linux
If code, which runtime stack: python/node
Create template: Queue trigger, ServiceBus Queue trigger, ServiceBus Topic trigger, Blob trigger, EventHub trigger, CosmosDB trigger, EventGrid trigger

Issues:
The connection string properties for any resource type have a default string (ex. CosmosDbConnectionString). This string is not a valid option (as in it is not one of the user's database/event hub/service bus etc connection strings) and it prevents us from picking a value from the list we get based on the resource type. In template v1, the default value for resource types is undefined and it works correctly.

This issue reproduces in production in both the new/old function create experience.

[shimedh]

@fabiocav / @soninaren / @vrdmr Can you look into fixing this?

[liliankasem]

@vrdmr can your team look into updating python templates?

[hallvictoria]

After creating a function using the V2 CosmosDB trigger template, if there are no existing settings and the customer continues, then only the template's default value (CosmosDbConnectionString) will be used.

For V1, if there are no existing settings and the customer does not create a new one, then the connection setting will be left blank.

In both scenarios, indexing will fail because no connection setting. What is the ask here?