Remove inlined request try/catch wrappers in favor of shared error handling

[rappm]

Summary

Remove the inlined try { ... } catch (err) { console.error(err); throw err } wrapper from every
query/mutation once the shared axios instance handles logging centrally.

Blocked on prompt-edu/prompt-shared-state#59 (shared request error handling).

What is duplicated (verified, ~130 files)

The identical wrapper across the network layers of assessment (~58), team_allocation (~21),
self_team_allocation (~12), certificate (~5), example (~1):

• clients/example_component/.../network/queries/getExampleInfo.ts:3
• clients/assessment_component/.../network/queries/getCoursePhaseParticipations.ts:6

Work

• After the shared response interceptor lands, strip the try/catch from the ~130 call sites so each
  function is just return (await instance.get/post(url)).data.

[rappm]

Still blocked. The upstream blocker prompt-edu/prompt-shared-state#59 is closed, but the shipped 1.2.0 factory does not actually carry the response error interceptor: createAuthenticatedAxiosInstance installs only the request interceptor, and logAndRethrow is attached separately to the two module-level singletons. logNetworkError is also not re-exported from the package, so consumers cannot attach it themselves.

Stripping the ~130 try/catch wrappers against 1.2.0 would silently drop all network error logging in the phase components. Filed prompt-edu/prompt-shared-state#78 to move the interceptor into the factory; this issue should wait for that release.

Context: #2068 adopted the factory across 6 phase components and deliberately left the wrappers in place for this reason.