Fix RandomX hashrate units

[Catnap7]

Summary

Fixes #3210 by making hashrate display units depend on the mining algorithm instead of always using graph-rate units.

This change:

• formats C29 mining with graph units (G/s, kG/s, MG/s, etc.)
• formats RandomX mining with hash units (H/s, kH/s, MH/s, etc.)
• passes RandomX explicitly from the CPU mining tile so macOS CPU mining no longer displays G/s
• adds formatter coverage for RandomX units

Verification

• npm test -- --run src/utils/formatters.test.ts — 62 tests passed
• npm exec tsc -- --noEmit
• git diff --check

Note: Vitest printed its existing "close timed out" warning after the tests passed, but exited successfully.

[gemini-code-assist]

Code Review

This pull request introduces support for the RandomX mining algorithm by adding it to the GpuMiningAlgorithm enum and updating the CPU mining tile to use it. It also modifies the formatHashrate utility to support different units ('G' for C29 and 'H' for RandomX) and includes corresponding unit tests. Feedback suggests replacing the ternary logic in formatHashrate with an explicit mapping to improve extensibility and handle other algorithms that might share the same units.

[gemini-code-assist]

The current ternary logic defaults to 'H' for any algorithm other than C29. This is fragile because other algorithms (like C31) also use Graph-rate units (G/s). Using an explicit mapping makes the code more robust and easier to extend as new algorithms are added, while also making the intent clearer.

    const unit = {
        [GpuMiningAlgorithm.C29]: 'G',
        [GpuMiningAlgorithm.RandomX]: 'H',
    }[algo];

[Catnap7]

Addressed in 0f098d81: formatHashrate now uses an explicit HASHRATE_BASE_UNITS mapping keyed by GpuMiningAlgorithm, with Record<GpuMiningAlgorithm, 'G' | 'H'> so future enum additions require an explicit unit choice at type-check time.

Re-ran npm test -- --run src/utils/formatters.test.ts, npm exec tsc -- --noEmit, and git diff --check.

[Catnap7]

Follow-up after another PR appeared for the same issue: I strengthened this PR so the algorithm type is no longer GPU-specific and the RandomX coverage is broader.

Added in 23248e96:

• renamed the frontend algorithm enum to shared MiningAlgorithm
• kept CPU mining explicitly passing MiningAlgorithm.RandomX
• kept C29 as the default graph-rate path for GPU/miner tiles
• added formatter coverage for RandomX H/s, kH/s, MH/s, and joinUnit=false

Re-verified locally:

• npm test -- --run src/utils/formatters.test.ts (65 tests passed)
• npm exec tsc -- --noEmit
• git diff --check