fix(flagd-provider): update fractional targeting test expectations for flagd v0.15.4

[jonathannorris]

Summary

• Updates color-palette-experiment fractional targeting test expectations to match bucketing behavior in flagd v0.15.4
• The fractional evaluator changed to high-precision integer arithmetic ((hash * totalWeight) >> 32), which rebucketed all users — tracked in [flagd] [FEATURE] Harden Hashing Consistency And Add Support For Non-string Attributes in Fractional Evaluation #73
• Expected values verified by running the exact twmb/murmur3 + distributeValue algorithm from flagd's source at core/v0.15.4
• Replaced targeting keys with ones that resolve to all four distinct variants (red, blue, green, grey), so the test validates fractional bucketing rather than falling through to the default
• Originally identified as a pre-existing failure in chore: resolve open dependabot security alerts #165

Also bumps BUNDLED WITH in the otel-hook Gemfile.lock from 2.7.1 to 4.0.11. A Ruby 4.1dev commit (between May 4–12) made Pathname::SEPARATOR_PAT private, breaking bundler 2.7.1's vendored thor. Bundler 4.0.0+ includes the fix (ruby/rubygems#9056).

[gemini-code-assist]

Code Review

This pull request updates the expected hex color values in the flagd provider's test suite for fractional targeting. Feedback suggests that the updated expectations are less effective because most keys now resolve to the default variant, making it difficult to verify if the fractional logic is functioning correctly or simply falling back to defaults. It is recommended to use targeting keys that map to a more diverse set of variants to ensure proper test coverage.

[jonathannorris]

is failing due to a Ruby 4.1dev regression — a commit between May 4–12 made Pathname::SEPARATOR_PAT a private constant. Both bundler 2.7.1 (original) and 4.0.11 (bumped in this PR) reference it directly, so both fail when running against the current ruby-head build.

The fix is already in bundler master (source/path.rb now uses pathname.absolute? instead), just not released yet. Marked the head matrix entry as continue-on-error: true so it doesn't block — it'll go green on its own once the next bundler release ships.