Add Sound page to the Programming Guide

[pushfoo]

Closes #1274
Closes #1900

Changes

1. Add link targets to the platformer tutorial
2. Add new Sound page to the programming guide covering usage and compatibility
3. Link the Sound page from the top-level index

How to Test

1. Clone the branch locally
2. Run pip install -I -e .[dev] to make sure you have the dev dependencies fully installed & upgraded
3. ./make.py html (optional, but helps prevent an occasional rebuild loop)
4. ./make.py serve
5. Open https://localhost:8000 in your browser
6. Verify the page is in the sidebar and Programming Guide homepage section
7. Open http://localhost:8000/programming_guide/sound.html
8. Proof-read the Sound Basics sections brutally:
   • http://localhost:8000/programming_guide/sound.html#sound-basics-loading
   • http://localhost:8000/programming_guide/sound.html#sound-basics-playing
   • http://localhost:8000/programming_guide/sound.html#sound-basics-stopping
9. Verify that #1900 is covered by http://localhost:8000/programming_guide/sound.html#backends-determine-playback-features
10. If time / interest allow, proof read and verify other parts

Follow-up work for future PRs

1. Move some of the preloading concepts to a new performance page / heading
2. Add an easier to digest reference counting section somewhere and link it instead of the Python contributor doc
3. Move some compatibility information to its own page / heading

[pushfoo]

@DavidEBrumbaugh Since you were the initial reporter for pyglet/pyglet#952, would you be up for building the doc locally and previewing it? I've updated the test steps with instructions for doing so.

[DavidEBrumbaugh]

This thing popped up back into my inbox I didn't see it initially I apologize if you still need me to look into it please let me know ⁣Get BlueMail for Android ​

…

On Oct 7, 2023, 3:18 AM, at 3:18 AM, Paul ***@***.***> wrote: @DavidEBrumbaugh Since you were the initial reporter for pyglet/pyglet#952, would you be up for building the doc locally and previewing it? I've updated the test steps with instructions for doing so. -- Reply to this email directly or view it on GitHub: #1922 (comment) You are receiving this because you were mentioned. Message ID: ***@***.***>

[pushfoo]

@DavidEBrumbaugh

I would appreciate it if you could verify the PulseAudio crash you reported is adequately covered by the Backends Determine Playback Features heading.

The doc about the crash will be relevant for another few months at the minimum. Although it seems like there is a fix in the works, it sounds like it may be delayed until pyglet 2.2.

If you're travelling without access to a fast connection, this may be the easiest approach:

1. Wait for this to merge
2. Wait for the readthedocs build to complete & add the new page
3. Once the build finishes, check the Backends Determine Playback Features heading at https://api.arcade.academy/en/development/programming_guide/sound.html (won't exist until this is merged & built)