fix: Propagation of annotations to TCPRoutes

[as51340]

Annotations used for Gateway will now also be also propagated to TCPRoute objects

[as51340]

Tracking

• [Link to Epic/Issue]

Standard development

• Update / add chart templates, values, and NOTES.txt as needed
• Run helm lint and helm template locally against the changed chart(s)
• Verify the chart installs and upgrades cleanly on a test cluster

Labels checklist

• Add a docs label (exactly one): docs-changelog-only, docs-needed, or docs-not-needed
• Add at least one component label: memgraph, memgraph-ha, memgraph-lab, or infrastructure
• Add at least one type label: bug, feature, or infrastructure
• Assign the PR to a milestone
  • If not known, set for a later milestone

Documentation checklist

• Write a release note, including added/changed clauses
  • Annotations used for Gateway will now also be propagated to TCPRoute objects. #270
  • What has changed? What does it mean for a user? What should a user do with it? [#{{PR_number}}]({{link to the PR}})
• [ Documentation PR link memgraph/documentation#XXXX ]
  • Is back linked to this development PR

[github-actions]

Release note advisory

Annotations used for Gateway will now also be also propagated to TCPRoute objects. #270

Valid format and correct PR link, but there's a minor grammatical typo: 'also be also propagated' should be 'also be propagated' (remove the extra 'also').