feat: refactor GlideBlock to resolve double-execution and timing issues (Fix #6917)

[gcharpe1604]

Description

This PR refactors the GlideBlock (glissando) implementation to remove the dependency on Singer.noteCounter. This resolves the "double-execution" bug where blocks inside the Glide clamp were run twice, causing unintended side-effects on variables and state. It also implements a buffering mechanism in the Singer engine to ensure perfectly synchronized glissando playback.

Related Issue

This PR fixes #6917

PR Category

• Bug Fix — Fixes a bug or incorrect behavior (Double-execution of blocks)
• Feature — Adds new functionality
• Performance — Improves performance
• Tests — Adds or updates test coverage

Changes Made

• Removed Singer.noteCounter from GlideBlock.flow in js/blocks/OrnamentBlocks.js.
• Implemented a glideBuffer in js/turtle-singer.js to collect notes during the synchronous execution of the glissando clamp.
• Added Singer.playGlideBuffer to handle synchronized audio triggering with precise Tone.now() offsets.
• Refactored Singer.processNote to unify synth trigger logic across instruments and voices.
• Updated js/blocks/__tests__/OrnamentBlocks.test.js to verify the new buffering and signal-based playback behavior.

[github-actions]

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

Coverage: Statements: 44.81% | Branches: 36.3% | Functions: 49.9% | Lines: 45.25%

[github-actions]

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

Coverage: Statements: 44.82% | Branches: 36.33% | Functions: 49.89% | Lines: 45.25%

[github-actions]

This PR has merge conflicts with master.

Please rebase your branch:

# Add upstream remote (one-time setup)
git remote add upstream https://github.com/sugarlabs/musicblocks.git

# Fetch latest master and rebase
git fetch upstream
git rebase upstream/master

# Resolve any conflicts, then:
git push --force-with-lease origin YOUR_BRANCH

Tip: Enable "Allow edits from maintainers" on this PR so we can auto-rebase for you next time. This only grants access to your PR branch. Your fork's other branches are not affected.

[github-actions]

🧪 Jest Test Results

❌ Some Jest tests failed. Please check the logs and fix the issues before merging.

Coverage: Statements: 47.56% | Branches: 38.82% | Functions: 52.43% | Lines: 47.97%

Note: These failures may be introduced by this PR or may already exist in the master branch.
Tip: Update your branch with the latest master and rerun tests.
If the same failures are present on master, they are likely not introduced by this PR.

Failed Tests:

LocalCard.test.js

[codecov]

Codecov Report

❌ Patch coverage is 78.26087% with 10 lines in your changes missing coverage. Please review.
✅ Project coverage is 59.30%. Comparing base (a76b8bb) to head (4c5015b).
⚠️ Report is 5 commits behind head on master.

Files with missing lines	Patch %	Lines
js/turtle-singer.js	61.53%	10 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6918      +/-   ##
==========================================
+ Coverage   59.28%   59.30%   +0.02%     
==========================================
  Files         176      176              
  Lines       57967    57995      +28     
==========================================
+ Hits        34365    34395      +30     
+ Misses      23602    23600       -2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

This PR has merge conflicts with master.

Please rebase your branch:

# Add upstream remote (one-time setup)
git remote add upstream https://github.com/sugarlabs/musicblocks.git

# Fetch latest master and rebase
git fetch upstream
git rebase upstream/master

# Resolve any conflicts, then:
git push --force-with-lease origin YOUR_BRANCH

Tip: Enable "Allow edits from maintainers" on this PR so we can auto-rebase for you next time. This only grants access to your PR branch. Your fork's other branches are not affected.