refactor(selection): drop residual concept-sector surface from sub-industry path

- remove the sector_type parameter from the selection port, adapter, and
  use case; the adapter now passes SectorType.INDUSTRY directly, deleting
  the dead concept vocabulary mapping
- stop parsing concepts/concept_total/concept_limit from the sector-radar
  membership response in the web API layer and narrow the response type to
  industries only
- update tests and the task PRD accordingly; backend pyright errors drop
  from the 16 baseline to 14

zhixing-web/src/features/sector-radar/api/sector-radar.api.test.ts

@@ -290,12 +290,6 @@ describe("stock sector membership adapter", () => {
     requested_trade_date: "2026-08-28",
     trade_date: "2026-08-28",
     industries: [{ code: "BK0901.DC", name: "银行" }],
-    concepts: [
-      { code: "BK0001.DC", name: "机器人" },
-      { code: "BK0002.DC", name: "人工智能" },
-    ],
-    concept_total: 2,
-    concept_limit: 20,
   }
 
   it("requests the snake-case endpoint and validates the payload", async () => {
@@ -316,8 +310,6 @@ describe("stock sector membership adapter", () => {
       status: "no_data",
       trade_date: null,
       industries: [],
-      concepts: [],
-      concept_total: 0,
     })
 
     const result = await getStockSectorMembership("000001.SZ", "2026-08-28")