Apply skip-time changes to a running player

[r0adkll]

Found while testing #607. On Android, changing the skip forward or back time in Settings → Playback updated the player's button labels straight away, but the actual skips kept the old amounts until the app restarted. ExoPlayer took its seek increments once, from the builder, when the player was created.

What changed

• ExoPlayerAudioPlayer collects observeForwardTimeMs() and observeBackwardTimeMs() in its main-thread scope, and pushes changes into ExoPlayer's runtime setSeekForwardIncrementMs / setSeekBackIncrementMs (added in Media3 1.11).
  • That covers the in-app buttons, the media notification and other media-session controls.
  • Desktop and iOS already read the skip times on every skip.
• A changelog entry under Fixed.

Verification

• ./scripts/ktlint --check passes, :app:android:compileAlphaDebugKotlin compiles, and :infra:audioplayer:impl:jvmTest passes.
• On device: the same change was verified on the emulator in the closed Apply skip-time changes to a running player #1198, in one app session without restarting. Each change took effect on the next skip, whether from the in-app buttons, cmd media_session dispatch fast-forward / rewind, or the notification buttons:

Skip times (forward / back)	Result
30s / 10s (unchanged)	+30s / −10s
changed to 5s / 30s	+5s / −30s
changed to 10s / 5s	+10s / −5s

🤖 Generated with Claude Code

[github-actions]

	Messages
📖	This PR has been checked by Danger

Generated by 🚫 Danger Kotlin against d155d34

[Rotom-Bot]

Code Coverage

Total Project Coverage	23.49%	❌

[github-actions]

Android APK @ d25fea3