feat: stream_routes resource in services

[SkyeYoung]

Please answer these questions before submitting a pull request, or your PR will get closed.

Why submit this pull request?

• Bugfix
• New feature provided
• Improve performance
• Backport patches

What changes will this PR take into?

Depend on #3103

This PR adds the function of displaying stream routes at the same level as the services detail.

Please note that since the admin API does not yet support filtering by service_id, all routes are currently displayed directly.

service_id will be auto set to form when add route

service_id will of course appear on the routes detail page

edit mode:

[Copilot]

Pull Request Overview

This pull request introduces a new "stream_routes" resource alongside the existing services detail view. Key changes include:

• Adding list, add, detail, and edit components for stream routes.
• Updating route generation to incorporate the new stream routes endpoints.
• Enhancing form context usage for read-only fields (e.g. "service_id") across different route modules.

Reviewed Changes

Copilot reviewed 18 out of 18 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
src/utils/form-context.ts	Introduces common form context for handling read-only fields.
src/routes/stream_routes/*	Implements listing, adding, and displaying stream routes.
src/routes/services/detail.$id/stream_routes/*	Integrates stream routes into the services detail view.
src/routes/routes/*	Refactors route listing and detail views to support updated patterns.
src/routeTree.gen.ts	Updates the route tree to include new stream routes endpoints.
src/components/page/ToAddPageBtn.tsx	Updates to support new route key patterns in add/detail buttons.
src/components/form-slice/FormPartRoute/index.tsx	Enhances form section by disabling fields based on read-only status.
src/apis/hooks.ts	Modifies hook generics to support extended list page keys.

Comments suppressed due to low confidence (1)

src/apis/hooks.ts:77

• Consider renaming the generic parameter 'U' to a more descriptive name (e.g. 'AlternateKey' or 'ExtendedKey') to improve code readability and maintain consistency.

export const genUseList = <T extends ListPageKeys, U extends ListPageKeys, P extends PageSearchType, R>(...) => {

[juzhiyuan]

Test locally & LGTM