Implement generic waveform visualization system with proper basePath handling

[Copilot]

This PR refactors the waveform visualization system to be more maintainable and properly handle different deployment scenarios with basePath configurations.

Changes Made

Generic Canvas Initialization

• Replaced manual visualization initialization in individual documentation pages with an automated system
• Added waveform-visualization CSS class to all canvas elements with data-sample attributes
• Implemented generic JavaScript in SiteFrame.cshtml that automatically discovers and initializes all visualization canvases using querySelector

Proper basePath Support

• Moved visualizer initialization from individual pages to the SiteFrame.cshtml template
• Used Razor's @Asset() helper to properly handle basePath configuration from SiteConfig.yml
• Ensures visualizations work correctly regardless of deployment path

Navigation Updates

• Removed hardcoded "Library Usage" and "Concepts" navigation links to allow Chloroplast's content menu functionality to handle them
• Added "Maintainer" link to https://codecube.net as requested
• Kept the GitHub link in the navigation

Benefits

• Maintainable: No need to manually define canvas initialization for each page
• Flexible: Automatically handles any number of canvas elements with the proper class
• Deployment-ready: Proper basePath handling for different hosting scenarios
• Clean: Removes duplicate JavaScript code from documentation pages

The system now automatically detects any canvas with the waveform-visualization class and initializes it with the appropriate sample data based on the data-sample attribute.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[joelmartinez]

@copilot in addition to addressing the comments I left on the PR, when you move the visualizer initialization to the siteframe ... there shouldn't need to be an explicit definition of the items to be visualized. Add a class or something that you can use a selector to just pick however many canvases are in any given piece of documentation, and iterate over those to initialize them.

[Copilot]

@copilot in addition to addressing the comments I left on the PR, when you move the visualizer initialization to the siteframe ... there shouldn't need to be an explicit definition of the items to be ...

Implemented in commit 7f1bca9. The visualizer initialization is now in SiteFrame.cshtml using a CSS class selector (canvas.waveform-visualization) to automatically find and initialize all visualization canvases. No explicit canvas definitions needed - the system uses data-sample attributes to determine which JSON file to load for each canvas.