feat(api-server): Improved api-server volume and like/dislike state

[rewhex]

This PR includes a couple of small but useful improvements to the api-server:

Volume State Endpoint:
The volume state endpoint now includes a new isMuted boolean. It was a single state volume level before, now it also has isMuted property, to detect whether volume button is pressed (just what the /v1/toggle-mute does).

New Like State Endpoint:
Added a new endpoint: GET /v1/like-state
It returns the current song's like/dislike status, using the same values: LIKE, DISLIKE, INDIFFERENT as YouTube Music already has.

[Copilot]

Pull Request Overview

This PR enhances the API server by extending volume state with mute information and introducing a new like/dislike state endpoint.

• Add VolumeState type with isMuted
• Introduce setup and IPC for like/dislike changes in the front-end provider
• Update MPRIS, song-controls, and backend routes to handle LikeType and VolumeState

Reviewed Changes

Copilot reviewed 7 out of 7 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
src/types/datahost-get-state.ts	Add VolumeState interface alongside existing enums
src/providers/song-info-front.ts	Implement setupLikeChangedListener and enrich volume IPC with isMuted
src/providers/song-controls.ts	Use LikeType enums for update-like IPC calls
src/plugins/shortcuts/mpris.ts	Adapt MPRIS handler to consume VolumeState and mute logic
src/plugins/api-server/backend/types.ts	Extend backend context type with LikeType and VolumeState
src/plugins/api-server/backend/routes/control.ts	Define new getLikeState route and update getVolumeState schema
src/plugins/api-server/backend/main.ts	Wire up ytmd:like-changed IPC and pass new getters to route registration

Comments suppressed due to low confidence (2)

src/plugins/api-server/backend/routes/control.ts:90

• Add tests for the new GET /api/v1/like-state endpoint and update tests for GET /api/v1/volume-state to verify the isMuted field is returned correctly.

  getLikeState: createRoute({

src/types/datahost-get-state.ts:48

• [nitpick] Consider adding a TSDoc comment above VolumeState to describe its purpose and fields (state vs isMuted) for clearer code documentation.

export interface VolumeState {

[rewhex]

@JellyBrick hello, I've fixed copilot's comments, can you please merge this PR?

[JellyBrick]

Is the use of MutationObserver strictly necessary in this part?

[rewhex]

Hmm, I don't think we can trigger state change by something else. Like any other controls (volume for example) we can get the buttons state with this and show it to the user.

Screenshot