Make it possible to add annotations to the keys secret

[sdahlbac]

Add command line option --keys-secret-annotations for specifying the annotations to be added to the keys secret when doing func kubernetes deploy

Tested manually using

--keys-secret-annotations reflector.v1.k8s.emberstack.com/reflection-allowed=true,reflector.v1.k8s.emberstack.com/reflection-auto-enabled=true,reflector.v1.k8s.emberstack.com/reflection-auto-namespaces=default

which renders the relevant bit of the keys secret like follows

...
kind: Secret
metadata:
  name: <name>
  annotations:
    reflector.v1.k8s.emberstack.com/reflection-allowed: "true"
    reflector.v1.k8s.emberstack.com/reflection-auto-enabled: "true"
    reflector.v1.k8s.emberstack.com/reflection-auto-namespaces: default

Issue describing the changes in this PR

resolves #3483

Pull request checklist

• My changes do not require documentation changes I do not know, does it?
  • Otherwise: Documentation issue linked to PR
• My changes do not need to be backported to a previous version
  • Otherwise: Backport tracked by issue/PR #issue_or_pr
• I have added all required tests (Unit tests, E2E tests)

I have not ran nor added tests as I have a mac.

[sdahlbac]

@microsoft-github-policy-service agree

[liliankasem]

/azp run coretools.public

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[liliankasem]

lgtm but I don't want to merge this in without tests; you should be able to write unit tests on a mac (it's my primary device as well). If you're not longer able to contribute to this PR, I can speak to the team about getting this reassigned!

[sdahlbac]

Is https://github.com/Azure/azure-functions-core-tools/blob/v4.x/CONTRIBUTING.md#running-the-test-suite incorrect then?

[liliankasem]

Is https://github.com/Azure/azure-functions-core-tools/blob/v4.x/CONTRIBUTING.md#running-the-test-suite incorrect then?

I believe it is outdated. It was written 7 years ago. My team just got ownership of this repo so we can work on updating this outdated information, but this might take some time given other priorities. You should be able to run tests like any normal c# project