What this PR does / why we need it

Adds optional pod-level scheduling knobs to the FeatureStore CR so users can place the operator-managed Deployment on specific nodes or on nodes with taints:

spec:
  services:
    nodeSelector:
      kubernetes.io/os: linux
    tolerations:
      - key: dedicated
        operator: Equal
        value: feast
        effect: NoSchedule

Both fields live on spec.services, alongside the existing affinity and topologySpreadConstraints. tolerations is applied directly to the pod spec. nodeSelector becomes the base selector, with the pre-existing per-server containerConfigs.nodeSelector overlaid on top (per-service wins on key conflicts), preserving the existing merge-with-mutating-webhook behavior.

Regenerated artifacts: deepcopy, CRD bases, dist/install.yaml, the API reference, and the OLM bundle.

Which issue(s) this PR fixes

N/A

Checks

• I've made sure the tests are passing.
• My commits are signed off (git commit -s)
• My PR title follows conventional commits format

Testing Strategy

• Unit tests
• Integration tests
• Manual tests
• Testing is not required for this change

Testing: added unit coverage for top-level nodeSelector, per-service override precedence, and tolerations. go build ./..., go vet ./..., and all non-e2e operator test packages pass.