Implement shutdown functionality for API layer with complete state reset

[Copilot]

This PR implements the ability to invoke shutdown from the API layer to gracefully clean up all registered providers during application shutdown.

Overview

The OpenFeature specification requires a shutdown mechanism to allow applications to properly clean up resources when terminating. Previously, the Ruby SDK only supported shutdown when switching providers individually, but lacked a global shutdown capability accessible from the API layer.

Implementation

Core Changes

1. Configuration shutdown method: Added a shutdown method to the Configuration class that iterates through all registered providers (both default and domain-specific) and calls their shutdown methods if available.

2. API layer exposure: Extended the API class to delegate the shutdown method from configuration, making it accessible at the API level.

3. Thread-safe operation: Leverages the existing @provider_mutex to ensure shutdown operations are thread-safe.

4. Complete state reset: The shutdown method now properly clears all providers and resets the SDK to its initial state after shutdown.

5. Graceful error handling: The implementation safely handles providers that don't implement a shutdown method without raising errors.

Usage

# Configure providers
OpenFeature::SDK.configure do |config|
  config.set_provider(MyProvider.new)
  config.set_provider(AnotherProvider.new, domain: "special_domain")
end

# During application shutdown
OpenFeature::SDK.shutdown

Shutdown Behavior

When OpenFeature::SDK.shutdown is called, it will:

1. Call the shutdown method on all registered providers that support it
2. Clear all registered providers from the configuration
3. Reset the SDK to its initial state

After shutdown, no providers will be available and the SDK will need to be reconfigured if you want to continue using it.

Custom Provider Implementation

For custom providers that need cleanup:

class MyProvider
  def shutdown
    # Perform any shutdown/reclamation steps with flag management system here
    # Return value is ignored
  end
end

Testing

• Added comprehensive test coverage for both Configuration and API level shutdown functionality
• Tests verify behavior with providers that do and don't implement shutdown methods
• Tests ensure thread-safety and proper handling of multiple domains
• Tests verify that providers are properly cleared after shutdown
• All existing tests continue to pass with 99.57% code coverage maintained

Documentation

Updated the README to:

• Mark the shutdown feature as fully implemented (✅)
• Provide complete usage examples with proper shutdown behavior
• Include guidance for custom provider implementations
• Remove the "Coming Soon" notice for this feature

The implementation follows existing patterns in the codebase and maintains backward compatibility while adding the requested functionality according to the OpenFeature specification.

Fixes #149.

---

💬 Share your feedback on Copilot coding agent for the chance to win a $200 gift card! Click here to start the survey.

[github-actions]

Hey there and thank you for opening this pull request! 👋🏼

We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:

No release type found in pull request title "Implement shutdown functionality for API layer with complete state reset". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - feat: A new feature
 - fix: A bug fix
 - docs: Documentation only changes
 - style: Changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc)
 - refactor: A code change that neither fixes a bug nor adds a feature
 - perf: A code change that improves performance
 - test: Adding missing tests or correcting existing tests
 - build: Changes that affect the build system or external dependencies (example scopes: gulp, broccoli, npm)
 - ci: Changes to our CI configuration files and scripts (example scopes: Travis, Circle, BrowserStack, SauceLabs)
 - chore: Other changes that don't modify src or test files
 - revert: Reverts a previous commit

[josecolella]

@copilot Check out https://openfeature.dev/blog/spec-0.6.0/#initialization-and-shutdown for spec information

[josecolella]

@copilot Here is the full spec documentation: https://openfeature.dev/specification/sections/flag-evaluation

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.56%. Comparing base (f983a3f) to head (161aa73).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #195   +/-   ##
=======================================
  Coverage   99.55%   99.56%           
=======================================
  Files          16       16           
  Lines         226      231    +5     
=======================================
+ Hits          225      230    +5     
  Misses          1        1           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

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

[Copilot]

@copilot Check out https://openfeature.dev/blog/spec-0.6.0/#initialization-and-shutdown for spec information

Thanks for pointing me to the OpenFeature specification! I reviewed the shutdown requirements and improved the implementation. The shutdown method now properly clears all providers after shutting them down, resetting the SDK to its initial state as expected by the spec.

Key improvements in commit 161aa73:

• Shutdown now clears all registered providers after calling their shutdown methods
• SDK resets to initial state for proper cleanup
• Updated tests verify providers are cleared after shutdown
• Documentation updated to reflect complete shutdown behavior

The implementation now fully complies with the OpenFeature specification for shutdown functionality.

@copilot Here is the full spec documentation: https://openfeature.dev/specification/sections/flag-evaluation

I reviewed the specification documentation and updated the shutdown implementation accordingly. The shutdown method now properly follows the OpenFeature spec by clearing all providers and resetting the SDK state after shutdown, rather than just calling shutdown on the providers.

Changes made in commit 161aa73:

• Complete state reset after shutdown
• Provider clearing after shutdown calls
• Enhanced test coverage for proper cleanup verification
• Updated documentation reflecting spec-compliant behavior