Support for adding annotations to deployments in Connect

[SamEdwardes]

Closes #793

---

Hey Posit Connect team, could you please review this PR. Details on the use case or in the issue mentioned above.

I deployed Connect using this chart and verified that the annotations correctly get set on the deployment:

# values.yaml
fullnameOverride: posit-connect

deployment:
  annotations:
    deployment-annotate: Nice its working

kubectl get deployment posit-connect -o json | jq '.metadata.annotations'
{
  "deployment-annotate": "Nice its working",
  "deployment.kubernetes.io/revision": "18",
  "meta.helm.sh/release-name": "posit-connect",
  "meta.helm.sh/release-namespace": "samedwardes-posit-team"
}

[lucasrod16]

This makes sense to me given the use case described in #793. Could you add a couple of helm unit tests to help prevent regressions? These cases should cover it:

• No annotations on the deployment by default
• Annotations are applied when deployment.annotations is set

Here are some test cases for the chronicle chart for reference:

helm/charts/posit-chronicle/tests/metadata_test.yaml

Lines 68 to 80 in 87ae10f

	- it: should skip annotations by default
	asserts:
	- notExists:
	path: metadata.annotations
	- it: should apply custom annotations if specified
	set:
	commonAnnotations:
	another: annotation
	asserts:
	- isSubset:
	path: metadata.annotations
	content:
	another: annotation

[SamEdwardes]

My editor auto-formatted on save, which caused the unintentional changes to older versions. These are purely formatting fixes, the only functional change is the new line added for 0.8.31.

[SamEdwardes]

Thank you @lucasrod16. I added some unit tests. They are passing. Please let me know if you have any other comments, or if the PR is ready to merge.

[lucasrod16]

LGTM! Thanks for this @SamEdwardes!