Use BoldM type for fault magnitudes in Magnitudes config

[AndrewRidden-Harper]

Summary

source_modelling 2026.6.1 introduces the BoldM magnitude NewType. This
updates the Magnitudes realisation config to use BoldM instead of float,
and makes call sites across the codebase consistent.

Changes

• Bump source_modelling dependency to >=2026.6.1 (pyproject.toml, uv.lock)
• Magnitudes.magnitudes and __getitem__ now use BoldM
• Cast floats to BoldM when constructing Magnitudes (gcmt_to_realisation,
  nshm2022_to_realisation, tests)
• Pass bold_m=True to moment.magnitude_to_moment for BoldM magnitudes,
  preserving the existing runtime default (generate_domain, realisation_to_srf)

Notes

• In nshm2022_to_realisation, the magnitudes dict is shared with
  nshmdb.most_likely_fault (whose dict[str, float] is invariant), so the
  Magnitudes(...) construction uses a scoped # ty: ignore[invalid-argument-type]
  — safe because BoldM is a float NewType (identity at runtime).

[gemini-code-assist]

Code Review

This pull request updates the workflow to use the BoldM type from source_modelling.magnitude_scaling for magnitudes instead of raw floats, ensuring proper magnitude scaling. This includes updating tests, script files, and dependency versions in pyproject.toml and uv.lock. The review feedback highlights a missing import of magnitude_scaling in gcmt_to_realisation.py which would cause a runtime NameError, and points out typos and incorrect syntax in a type-ignore comment in nshm2022_to_realisation.py.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[lispandfound]

LGTM barring the conversion of magnitude types in gcmt-to-realisation.