Add Jest tests for musicutils.js to address zero test coverage

[swapnachoudhary43]

What this PR does

Adds proper Jest test coverage for js/utils/musicutils.js

Background

musicutils.js is one of the largest and most critical files in the
codebase (4427 lines) containing core music utility functions —
MUSICALMODES, PITCHES, key signature logic, and interval calculations.
Without any test coverage, regressions in these functions enter
production silently.

What this adds

Updated file js/utils/tests/musicutils.test.js covering:

• Real imports of exported functions and constants
• MUSICALMODES validation (major, minor, chromatic, ionian, aeolian)
• _calculate_pitch_number with enharmonic consistency checks
• getPitchInfo for string and numeric inputs
• setOctaveRatio / getOctaveRatio behavior
• reducedFraction with correct string output assertions
• NOTESSHARP and NOTESFLAT array validation
• isInt and noteIsSolfege utility checks

Changes made

• Removed unrelated files (tempCodeRunnerFile.js, themes.css)
• Replaced string-based file assertions with real function imports
• Tests now validate actual exported behavior, not just file contents

Tests

All 349 tests pass.
Full suite: 1 suite passing, 0 failures.

Related

• Closes [Bug]musicutils.js has zero Jest test coverage — regression risk for core music functions #6469
• • Tests
• Part of GSoC 2026 Music Blocks Maintenance work

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[mahesh-09-12]

@swapnachoudhary43 I had pointed out earlier about unrelated files, they're still present here, so please clean those up first. Also, the 0% coverage claim doesn't match what I'm seeing locally for musicutils.js, so it would be good to re-check how coverage was measured before adding more tests.

[Chaitu7032]

@swapnachoudhary43

Please keep this PR focused on musicutils.js tests, remove the accidental temp file, and replace string-based assertions with tests that actually import and validate the exported behavior of musicutils.js functions/constants.

[Ashutoshx7]

Unrelated changes in the pr
please remove it

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[mahesh-09-12]

@swapnachoudhary43 this PR includes unrelated files and commits, since the goal is to add tests for musicutils.js, the diff should be scoped only to that, please clean up the history and remove unrelated changes.
and also it looks like some of these tests already exist or overlap with current coverage. Can you clarify what new behavior is actually being tested here?

[github-actions]

✅ All Jest tests passed! This PR is ready to merge.

[vanshika2720]

Hi @swopnachoudhary43! While testing #6471, I found an issue in noteToPitchOctave it doesn’t handle multi-digit octaves (e.g., C10) or double sharps (e.g., Cx4).
To make this PR more robust, it would be great to switch to _parse_pitch_string and export core constants like A0 and SOLFEGECONVERSIONTABLE for better edge-case coverage.