Standardize proxy port field in MCPRemoteProxy

[slyt3]

Description:

This PR aligns MCPRemoteProxy with MCPServer by standardizing the proxy port field naming.

Summary

• Added proxyPort to MCPRemoteProxySpec
• Deprecated the legacy port field
• Preserved backward compatibility during the transition

Details

• GetProxyPort() now resolves ports in the following order:
  1. proxyPort
  2. port
  3. default (8080)

• Updated controller and deployment tests

• Added test coverage to ensure proxyPort takes precedence over port

• Verified existing resources using port continue to work

This improves API consistency across MCP resources while maintaining a smooth migration path for existing users.

Fixes #3102

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 64.17%. Comparing base (7a16b10) to head (3e91f4f).
⚠️ Report is 12 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3257      +/-   ##
==========================================
+ Coverage   63.65%   64.17%   +0.52%     
==========================================
  Files         361      365       +4     
  Lines       35449    35248     -201     
==========================================
+ Hits        22566    22622      +56     
+ Misses      11072    10817     -255     
+ Partials     1811     1809       -2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dmjb]

This looks like a worthwhile change to me. @ChrisJBurns @JAORMX any concerns?

[dmjb]

@slyt3 You'll need to regenerate the CRDs. From the base of the project, run:

cd cmd/thv-operator/
task crdref-gen

[slyt3]

@slyt3 You'll need to regenerate the CRDs. From the base of the project, run:

cd cmd/thv-operator/

task crdref-gen

Done

[dmjb]

@slyt3 Looks good, but you'll also need to bump the helm chart under ./deploy/charts/operator-crds/Chart.yaml

After doing that, you may need to run task docs to update helm chart documentation.

[ChrisJBurns]

@dmjb I remember being in favour of this but I think @JAORMX had some comments on it in a previous PR.

[slyt3]

@slyt3 Looks good, but you'll also need to bump the helm chart under ./deploy/charts/operator-crds/Chart.yaml

After doing that, you may need to run task docs to update helm chart documentation.

done :)

[slyt3]

Uh, I had multiple Helm validation failures and CI compatibility issues,

Its really IMPORTANT, because this is significant stabilization changes. Its started with minor update, but it evolved to kinda huge.

its important because Pipeline unblocked after I upgraded cosign and CI caching to fix persistent release and CI failures. also removed hardcodede UIDs from helm charts. soo it will allow project to run on restrcited platforms like OpenShift.

[dmjb]

@slyt3 It looks like you included some changes to the github actions, and I see your comment about running into various problems. We haven't noticed any issues with the CI in our repo, were you trying to run them in your repo?

[dmjb]

I would like to see an explanation of why this is necessary

[slyt3]

so this cache is just pre-commit tool env. ~/.cache/pre-commit it just avoids redownloading and reinstalling tools like heml-docs and other depend. on every CI run. Withouit it, each workflow execution would spend extra time setting up the same tools from 0 and it just slow down the pipeline

[slyt3]

The CRD changes were already bumped to 0.0.95 earlier in this PR. have to bump to 0.0.96 to satisfy the linter.