fix: Align FeatureFlagSource CRD defaults with documentation

[Y0sh1dk]

This PR

Aligns FeatureFlagSource CRD defaults with what is stated in the documentation.

Related Issues

Fixes #837

How to test

• See Standalone Flagd deployment missing liveness/readiness probes #837

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 69.42%. Comparing base (499661e) to head (c08f437).
⚠️ Report is 99 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff             @@
##             main     #838       +/-   ##
===========================================
- Coverage   86.51%   69.42%   -17.10%     
===========================================
  Files          19       31       +12     
  Lines        1587     2008      +421     
===========================================
+ Hits         1373     1394       +21     
- Misses        173      561      +388     
- Partials       41       53       +12     

Files with missing lines	Coverage Δ
api/core/v1beta1/featureflagsource_types.go	89.10% <ø> (ø)

... and 25 files with indirect coverage changes

Flag	Coverage Δ
unit-tests	69.42% <ø> (∅)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

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

[gemini-code-assist]

Code Review

This pull request introduces default values for the RolloutOnChange, ProbesEnabled, and DebugLogging fields in the FeatureFlagSource CRD by adding +kubebuilder:default markers to the Go types and updating the corresponding YAML schema. It also includes a minor formatting adjustment to the FeatureFlagSourceStatus struct. The review feedback suggests reordering the +optional and +kubebuilder:default markers to maintain consistency with existing field definitions in the codebase.

[beeme1mr]

Thanks @Y0sh1dk! I'm going to ignore the codecov error since it's just a documentation change.