- Introduced a new test file for ResourceLimiter, covering various scenarios including disabled state, bucket selection based on compute units, concurrency limits, queue timeouts, context cancellation, and memory limits.
- Implemented tests for execution errors and metrics tracking to ensure accurate monitoring of request handling.
- Added benchmarks for performance evaluation under different load conditions.
- Enhanced test coverage for mixed request types and memory reservation release.
- Verified error messages for queue full and max concurrent scenarios.

- Added debug logging for queue depth upon request enqueuing and rejection due to full queue.
- Improved memory monitoring logs to include current queue depths for heavy and normal buckets.
- These enhancements facilitate better tracking and debugging of resource management behavior in the system.

- Updated goroutine closures in the ResourceLimiter tests to use the loop variable directly, ensuring proper indexing for concurrent requests.
- Simplified the memory threshold check in the ResourceLimiter implementation for clarity and efficiency.

…nto provider_resource_limiter

- Updated goroutine closures in the ResourceLimiter tests to pass the loop index as a parameter, ensuring accurate indexing for concurrent requests.
- This change prevents data races and ensures that results are stored correctly in the results slices during concurrent execution.

- Updated the Acquire method in ResourceLimiter to include a nil check for the ResourceLimiter instance, ensuring robustness when the instance is not initialized.
- This change prevents potential nil pointer dereference errors and maintains the intended functionality when the resource limiter is disabled.

…ency and queue size

- Updated the NewResourceLimiter function to accept additional parameters for heavy and normal bucket configurations, including maximum concurrent requests and queue sizes.
- Enhanced the SetupEndpoint method to retrieve these new configuration values from viper, ensuring flexibility in resource management settings.
- This change improves the adaptability of the resource limiter to varying load conditions and usage patterns.

…ation

- Added a new struct for resource limiter options to encapsulate configuration parameters such as memory threshold, CU threshold, and concurrency settings.
- Updated the RPCProvider to utilize the new resource limiter options, enhancing the flexibility of resource management.
- Modified the SetupEndpoint method to retrieve resource limiter settings from the new struct, streamlining the initialization process.

- Enhanced the Relay method in RPCProviderServer to ensure proper session cleanup when a request is rejected by the resource limiter.
- Added a call to OnSessionFailure to unlock the session, rollback CU deltas, and prevent session leaks.
- Improved error logging for cleanup failures to aid in debugging and monitoring.

- Updated the ResourceLimiter to accept an endpoint name during initialization, allowing for differentiated metrics per endpoint.
- Modified the NewResourceLimiter and related functions to incorporate the endpoint name, improving metric tracking and clarity.
- Adjusted tests to reflect the new parameter, ensuring comprehensive coverage of the updated functionality.

- Added a check in the ResourceLimiter's processQueue method to skip requests that have already been canceled or timed out.
- Implemented logging for skipped requests to aid in debugging and monitoring of request handling.
- This change improves the robustness of the resource limiter by preventing the execution of invalid requests.