fix: use mass and energy consistently for single phase solvers #9856

Job	Run time
semantic_pull_request	2s
is_not_draft_pull_request	4s
if_not_unassigned_pull_request	7s
baseline_log	3s
are_submodules_in_sync	9s
code_coverage / build_test_deploy	5s
Check code style / build_test_deploy	1m 19s
Check documentation / build_test_deploy	1m 2s
Ubuntu (20.04, gcc 10.5.0, open-mpi 4.0.3) - github codespaces / build_test_deploy	26m 14s
Ubuntu (20.04, gcc 9.4.0, open-mpi 4.0.3) / build_test_deploy	26m 15s
Ubuntu (22.04, clang 15.0.7, open-mpi 4.1.2) / build_test_deploy	26m 15s
Ubuntu (22.04, gcc 12.3.0, open-mpi 4.1.2) / build_test_deploy	26m 14s
Ubuntu debug (20.04, gcc 10.5.0, open-mpi 4.0.3) - github codespaces / build_test_deploy	26m 12s
Ubuntu (22.04, gcc 11.4.0, open-mpi 4.1.2) / build_test_deploy	26m 14s
Pangea 3 CUDA (AlmaLinux 8.8, gcc 9.4.0, open-mpi 4.1.2, cuda 11.5.0, openblas 0.3.10) / build_test_deploy	7s
Rockylinux CUDA (8, clang 17.0.6, cuda 12.5.1) / build_test_deploy	6s
Rockylinux CUDA (8, gcc 8.5, cuda 12.5.1) / build_test_deploy	6s
Ubuntu CUDA (20.04, clang 10.0.0 + gcc 9.4.0, open-mpi 4.0.3, cuda-11.8.89) / build_test_deploy	5s
Ubuntu CUDA debug (20.04, clang 10.0.0 + gcc 9.4.0, open-mpi 4.0.3, cuda-11.8.89) / build_test_deploy	6s
run_integrated_tests	1s
check_that_all_jobs_succeeded	1s
	2h 40m 47s

Provide feedback