Feature/rate limiter http

[archit-2003]

This PR introduces a built-in rate limiting capability for interservice HTTP calls within Gofr.

Tasks Completed:

• Introduced RateLimiterConfig struct: This new struct allows configuration of rate limits via RequestsPerSecond and Burst parameters.
• Integrated as an optional parameter to AddHTTPService: A service.WithRateLimiter option is now available to apply rate limiting when defining HTTP services.
• Applied rate limiting per target service: Each service configured with WithRateLimiter gets its own independent rate limiter instance, ensuring isolation.
• Included observability for rate limit events:
  • Logging: Clear log messages are generated when a rate limit is exceeded using the Logger interface.
  • OpenTelemetry Tracing: An OpenTelemetry event is added to the active span for rate-limited requests.
  • Prometheus Metrics: A Prometheus counter (app_http_service_rate_limit_exceeded_total) is incremented upon rate limit triggers.

Technical Details / Files Changed:

• pkg/gofr/service/ratelimiter.go: New file defining RateLimiterConfig and the core rate limiting logic.
• pkg/gofr/service/options.go: Modified to include the WithRateLimiter option.
• pkg/gofr/service/new.go: Modified to correctly initialize and inject dependencies into the rate limiter.
• (Optional: examples/using-http-service/main.go): Modified for local testing demonstration.

[Umang01-hash]

• There are no tests added for the new code.
• Documentation is not provided.
• Removes the current godoc comments at many places.
• Version changes are unncessary and should be removed.
• The way we are injecting Rate Limiter doesn't comply with what we are currently following for other HTTP options. Let's try to stick to the previous way only.

[Umang01-hash]

This change is not required. Please revert it.

[Umang01-hash]

Sorry, but any particular reason for removing these godoc comments??

[Umang01-hash]

If you need to add this option manually instead of doing:

svc = o.AddOption(svc)

i think the implementation is wrong. For the other configs/features we are not additionally providing the logger metrics etc then why for rate limiter??

[archit-2003]

Sure, I’ll review the implementation again and make the necessary updates. Thanks for the feedback!

[Umang01-hash]

Why this change?
I think sticking to :

a.AddHTTPService("cat-facts", "https://catfact.ninja",
	service.NewAPIKeyConfig("some-random-key"),
	service.NewBasicAuthConfig("username", "password"),
	
    &service.CircuitBreakerConfig{
       Threshold: 4,
       Interval:  1 * time.Second,
  },

   &service.DefaultHeaders{Headers: map[string]string{"key": "value"}},

   &service.HealthConfig{
       HealthEndpoint: "breeds",
  },
   service.NewOAuthConfig("clientID", "clientSecret",
	   "https://tokenurl.com", nil, nil, 0),

  &service.RetryConfig{
      MaxRetries: 5
  },
)

Is better?

[Umang01-hash]

Hey! @archit-2003. Thankyou for your contribution. Currently your PR has the below linter issues. Please resolve all the linters to completely pass the workflow.