[Feat]: Load manifest.yaml in skill.manifest for all registry skills

[rosspeili]

Feature Description

#165 fixed finance/wallet_screening so skill.manifest loads manifest.yaml from the bundle directory (same pattern as office/pdf_form_filler). The other nine registry skills still return a hardcoded partial dict (name, version only) from the @property, which can drift from manifest.yaml and breaks the contract that bundle tests and loaders expect.

Update every skill under skills/ to load manifest.yaml in skill.manifest, and ensure co-located test_skill_manifest_consistency asserts full parity (at minimum name, version, issuer where present).

Rationale

• Prevents repeat of [Bug]: [wallet_screening]: skill.manifest returns {} instead of loading manifest.yaml #165 (empty or stale skill.manifest).
• Aligns with CONTRIBUTING bundle standard and ai_native_workflow verification checklists.
• Keeps PyPI-shipped bundle metadata truthful for agents and maintainers.

Implementation Idea

1. Reuse the pdf_form_filler / wallet_screening pattern: read manifest.yaml beside skill.py, return {} only if missing.
2. Touch skills/**/skill.py for all registry skills (10 today).
3. Extend bundle tests where needed; optional maintainer sweep in tests/test_skill_issuer.py or per-skill maintainer tests.
4. CHANGELOG [Unreleased] → Fixed.

[rosspeili]

Still 4 skills on main return a hardcoded stub from skill.manifest instead of loading manifest.yaml: mica_module, pii_masker, prompt_rewriter, novelty_extractor.

Optional same PR: add a small shared helper on BaseSkill so we don’t copy the YAML-load block into every skill.py. #174 should follow the same pattern when it lands.