047_* CSR-Subscription notification tests — fixture & assertion fixes
The `047_*` Context-Source-Registration-Subscription notification tests carry several fixture/assertion problems (broker behaviour is correct throughout):
- **Entity-type mismatch** (047_03/04/08/09/16): the CSR-sub and the CSR fixtures register different entity types, so no notification fires and the test times out. Rework the fixture pair so the scopes overlap.
- **Hard-coded CSR ids in assertions** (047_03_01/04_01/08_01/09_01/16_01): the assertion compares against a literal CSR id instead of the actually-created one — substitute the real id.
- **Omitted `notificationTrigger`** (041_01_01/041_02_03): the broker adds the §5.2.6.5.2 default; fixtures/expectations should include it.
- **Stale expectation fields** (047_05_01/06_01): expectations predate `timesFailed`/`status` — regenerate against a current broker.
- **PATCH /csourceSubscriptions without @context** (047_16_01/16_03): the PATCH omits the @context so selector terms expand differently than the CSR's — send the same @context.
- **047_02_01** asserts two different CSR ids — align the variable indirection.
- **038_01_01/039_01_01/040_01_01** persist spec defaults in CSR-Sub expectations (§5.2.6.5.2) — decide and apply consistently.
issue