feat: Support referencing TwingateGroup from TwingateResourceAccess

[ekampf]

Related Tickets & Documents

• Issue: Support group creation and reference #364

Changes

• Added groupRef to TwingateResourceAccess CRD
• Some improvement to integration test - when re-run from failed, the CI run number doesnt change which caused re-runs to not work. So added better randomization for resource names to allow rerunning

Usage Example:

apiVersion: twingate.com/v1beta
kind: TwingateResource
metadata:
  name: my-twingate-resource
spec:
  name: My K8S Resource
  address: my.default.cluster.local
  alias: mine.local
---
apiVersion: twingate.com/v1beta
kind: TwingateGroup
metadata:
  name: test-group
spec:
    name: Test Group
---
apiVersion: twingate.com/v1beta
kind: TwingateResourceAccess
metadata:
  name: my-twingate-resource
spec:
  resourceRef:
    name: my-twingate-resource
  groupRef:
    name: "test-group"

[linear]

OSS-42 Support group creation and reference

[coveralls]

Pull Request Test Coverage Report for Build 11002532960

Details

• 28 of 30 (93.33%) changed or added relevant lines in 3 files are covered.
• 1 unchanged line in 1 file lost coverage.
• Overall coverage decreased (-0.1%) to 94.846%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
app/crds.py	20	22	90.91%

Files with Coverage Reduction	New Missed Lines	%
app/crds.py	1	97.75%

Totals
Change from base Build 10999237471:	-0.1%
Covered Lines:	975
Relevant Lines:	1014

---

💛 - Coveralls

[liorr]

LGTM