refactor(node): organize api tests into separate modules

[imabdulbasit]

api.rs was ~9.5k lines: ~1.9k of API code and ~7.6k of inline tests. This pulls the tests out into their own files without touching test logic.

• api::test_helpers and api::api_tests each move to their own file.
• The ~60 tests in api::test split into seven domain files under api/test/: endpoints, catchup, upgrades, rewards, stake_table, light_client, and namespace. Shared imports and helpersstay in api/test/mod.rs

[gemini-code-assist]

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

[claude]

Claude finished @imabdulbasit's task in 0s —— View job

---

I'll analyze this and get back to you.