feat: implementing project_plan_limits method to get limits from a new internal api endpoint

[geekbrother]

Description

This PR implements a new project_plan_limits method to get limits from the new internal https://api.reown.com endpoint to check the projectId and quota validation.

The full context is in the Slack thread.

How Has This Been Tested?

Tested manually.

Due Diligence

• Breaking change
• Requires a documentation update
• Requires a e2e/integration test update

[Copilot]

Pull Request Overview

This PR implements a new project_plan_limits method to integrate with a new internal API endpoint for retrieving project limits and quota validation, expanding from the existing explorer-based project data retrieval.

• Adds new project_limits and project_data_with_limits methods to the RegistryClient trait
• Introduces new data structures PlanLimits and ProjectDataWithLimits for handling limit information
• Refactors the HTTP client to support both explorer and internal API endpoints

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
src/registry/client.rs	Main implementation adding new methods, internal API URL support, and refactoring existing URL building logic
src/project/types/project_data.rs	Defines new data structures for plan limits and project data with limits
.github/workflows/ci.yaml	Updates toolchain from nightly to stable for formatting check

Comments suppressed due to low confidence (4)

src/registry/client.rs:17

• [nitpick] The variable name INTERNAL_API_BASE_URI uses URI but the type is Url. For consistency, consider renaming to INTERNAL_API_BASE_URL to match the type and other variable names in the codebase.

static INTERNAL_API_BASE_URI: Lazy<Url> =

src/registry/client.rs:225

• The new build_internal_api_url function lacks test coverage. Consider adding tests similar to the existing test_build_explorer_url tests to ensure the URL construction works correctly with query parameters.

fn build_internal_api_url(base_url: &Url, project_id: &str) -> Result<Url, url::ParseError> {

src/registry/client.rs:201

• The new project_limits method lacks test coverage. Consider adding integration tests to verify the method correctly handles valid project IDs, invalid project IDs, and various HTTP response scenarios.

    async fn project_limits(&self, project_id: &str) -> RegistryResult<Option<PlanLimits>> {

src/registry/client.rs:205

• The new project_data_with_limits method lacks test coverage. Consider adding tests to verify the method correctly combines project data and limits, and handles cases where either request fails.

    async fn project_data_with_limits(

[chris13524]

Why change this? We typically use nightly formatting which was fine

[geekbrother]

I believe we moved to the stable in a recent service change. As I remember, the reason to use nightly was an async trait, which is not an issue for a while. btw, blockchain-api uses a stable.