Feat: add NodeSelector to jaeger collector, query, and ingestor

[AhmedGrati]

Which problem is this PR solving?

• Resolves jaegeroperator to support nodeSelector #1351.

Short description of the changes

• Update collector, query, and ingester CRD.
• Add unit tests of the previous changes.

[frzifus]

Thanks for taking care of it @AhmedGrati!

[codecov]

Codecov Report

Patch coverage: 100.00% and project coverage change: +0.03 🎉

Comparison is base (5e1bc59) 87.47% compared to head (8b05e93) 87.50%.

❗ Current head 8b05e93 differs from pull request most recent head 21c6ae7. Consider uploading reports for the commit 21c6ae7 to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2200      +/-   ##
==========================================
+ Coverage   87.47%   87.50%   +0.03%     
==========================================
  Files         100      100              
  Lines        6890     6908      +18     
==========================================
+ Hits         6027     6045      +18     
  Misses        658      658              
  Partials      205      205              

Impacted Files	Coverage Δ
apis/v1/jaeger_types.go	87.50% <ø> (ø)
pkg/deployment/collector.go	100.00% <100.00%> (ø)
pkg/deployment/ingester.go	94.77% <100.00%> (+0.21%)	⬆️
pkg/deployment/query.go	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[AhmedGrati]

@frzifus do you have an idea about the issue? it seems that it's irrelevant to the PR.

[frzifus]

Not sure, i will try to look into it in the next days.

[AhmedGrati]

@frzifus I think it's ready now.
As for the Run miscellaneous E2E tests, I saw that it's been failing for a while, and we can fix it in another PR if you want.

[frzifus]

As for the Run miscellaneous E2E tests, I saw that it's been failing for a while, and we can fix it in another PR if you want.

I triggered a re-run - fixing the flaky test would be awesome :)