[TT-11299] Add missing orgId while using ingress

[buraksekili]

trafficstars

Description

This PR adds missing OrgID to ApiDefinition CRs created by Ingress controller.

Related Issue

https://tyktech.atlassian.net/browse/TT-11299

Motivation and Context

Test Coverage For This Change

• Update ApIDefinition CRDs since the fix introduces a new field in the status field. New CRD definitions can be found here
• Run Operator and confirm that OrgID is part of ApiDefinition's spec which is created by ingress controller.

Screenshots (if appropriate)

Types of changes

• [x] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• [ ] Make sure you are requesting to pull a topic/feature/bugfix branch (right side). If PRing from your fork, don't come from your master!
• [ ] Make sure you are making a pull request against our master branch (left side). Also, it would be best if you started your change off our latest master.
• [ ] Make sure you are updating CHANGELOG.md based on your changes.
• [ ] My change requires a change to the documentation.
  • [ ] If you've changed APIs, describe what needs to be updated in the documentation.
• [ ] I have updated the documentation accordingly.
• [ ] If you've changed API models, please update CRDs.
  • [ ] make manifests
  • [ ] make helm
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.
• [ ] Check your code additions will not fail linting checks:
  • [ ] gofmt -s -w .
  • [ ] go vet ./...
  • [ ] golangci-lint run

[sonarqubecloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
25.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud