When client is disabled, but metrics are not, metrics are referenced but never initialized.

[jdurkee-mdsol]

Describe the bug

When disabling the client but not disabling metrics, the metrics attribute/container is never initialized. Yet, attempting to call enabled? on the client results in undefined method ... for nil:NilClass as it attempts to access metrics.

Steps to reproduce the bug

Unleash::Client.new(
  disable_client: true,
  url: 'https://example.com',
  bootstrap_config: Unleash::Bootstrap::Configuration.new(
    data: '{
      "version": 1,
      "features": [
        {
          "enabled": true,
          "name": "featureX"
        }
      ]
    }'
  )
).enabled?('featureX', nil)

Expected behavior

No runtime errors, and correct state of the feature.

Logs, error output, etc.

[2023-05-01T18:45:55.551253+00:00          Unleash WARN ] : Unleash::Client is disabled! Will only return default (or bootstrapped if available) results!
/shared/unleash/lib/unleash/feature_toggle.rb:30:in `is_enabled?': undefined method `increment' for nil:NilClass (NoMethodError)

      Unleash.toggle_metrics.increment(name, choice) unless Unleash.configuration.disable_metrics
                            ^^^^^^^^^^
        from /shared/unleash/lib/unleash/client.rb:50:in `is_enabled?'
        from unleash_client.rb:77:in `<main>'

Screenshots

No response

Additional context

No response

Unleash version

Ruby SDK 4.4.2

Subscription type

Enterprise

Hosting type

Hosted by Unleash

SDK information (language and version)

Ruby SDK 4.4.2