We shouldn't be generating function keys for non http functions

If you create a queue triggered function in the portal, we end up generating a function secret file for that function that includes a function key. However, function secrets are only used for http functions.

Related portal issue here: https://github.com/Azure/azure-functions-ux/issues/1511

Reproduce the portal-created queue-triggered function and inspect the generated function secret file; the related portal issue is Azure/azure-functions-ux#1511. The work is done when non-HTTP functions no longer receive a function key, while HTTP functions retain the expected secrets behavior.

Written by the indexing model from the issue text.