Enable Ruby OpenFeature evaluation on older weblogs

[leoromanovsky]

Motivation

APM needs Ruby Feature Flags validation beyond the newest Rails weblog. The oldest Ruby system-tests image that can use the current OpenFeature SDK line is Ruby 3.1, so this broadens non-metric flag evaluation coverage to that floor.

Changes

• Add the OpenFeature SDK dependency and /ffe evaluation endpoints to the Sinatra 4.1 weblog used by uds-sinatra.
• Enable tests/ffe/test_dynamic_evaluation.py for uds-sinatra on Ruby 3.1, keep rails72, and add direct sinatra41.
• Leave exposure, EVP, and OTel metric test declarations unchanged.

Decisions

• Use openfeature-sdk ~> 0.5.1 instead of a broader ~> 0.5 range so Ruby 3.1 does not resolve the Ruby 3.4-only 0.6.x line.
• Treat Ruby 3.1 as the oldest practical OpenFeature system-test target because the current useful OpenFeature Ruby SDK line requires Ruby >= 3.1.
• Keep OTel metrics scoped to rails72; this PR is for core flag evaluation behavior, not hook-heavy metrics validation.

Related PRs

• Ruby implementation: feat(open_feature): emit server-side EVP flagevaluation dd-trace-rb#5896
• Ruby OpenFeature system-tests surface: Enable Ruby OpenFeature evaluation on older weblogs #7199
• Ruby OpenFeature runtime documentation: Document Ruby OpenFeature runtime recommendation documentation#37674

[github-actions]

CODEOWNERS have been resolved as:

manifests/ruby.yml                                                      @DataDog/ruby-guild @DataDog/asm-ruby
utils/build/docker/ruby/sinatra41/Gemfile                               @DataDog/ruby-guild @DataDog/asm-ruby @DataDog/system-tests-core
utils/build/docker/ruby/sinatra41/Gemfile.lock                          @DataDog/ruby-guild @DataDog/asm-ruby @DataDog/system-tests-core
utils/build/docker/ruby/sinatra41/app.rb                                @DataDog/ruby-guild @DataDog/asm-ruby @DataDog/system-tests-core