Test: remove no longer needed custom configs

[dominikvagner]

Warning

This will need to update the test-utils ref and merge that together, with those changes!

Summary

These custom dynamic configs aren't going to be needed after client changes done in "test-utils", they will be dynamic by default.

Testing steps

All tests pass.

#testwith content-services/content-sources-backend#1453

[sourcery-ai]

Hey - I've left some high level feedback:

• Now that the dynamic API client is injected via the client fixture, consider encapsulating the remaining ensureValidToken(..., '<TOKEN>.json', ...) + API call patterns (e.g., the polling block in CanUpdateSystemWithTemplate) into a small helper so token file names and validity checks aren’t duplicated and stay consistent across tests.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Now that the dynamic API client is injected via the `client` fixture, consider encapsulating the remaining `ensureValidToken(..., '<TOKEN>.json', ...)` + API call patterns (e.g., the polling block in `CanUpdateSystemWithTemplate`) into a small helper so token file names and validity checks aren’t duplicated and stay consistent across tests.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[sourcery-ai]

Hey - I've left some high level feedback:

• In CanUpdateSystemWithTemplate.spec.ts, now that the shared client is used for API calls, consider encapsulating or removing the explicit ensureValidToken(page, 'LAYERED_REPO_TOKEN.json', 5) in the polling step to avoid duplicated token-handling logic between the client fixture and the tests.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- In `CanUpdateSystemWithTemplate.spec.ts`, now that the shared `client` is used for API calls, consider encapsulating or removing the explicit `ensureValidToken(page, 'LAYERED_REPO_TOKEN.json', 5)` in the polling step to avoid duplicated token-handling logic between the client fixture and the tests.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[katarinazaprazna]

Looks great! The code feels a lot cleaner now. Thanks! ✨