internal/pipewire: respond to Core::Ping

There is currently no known message that will get the PipeWire server to emit this event. It should be handled regardless.

Signed-off-by: Ophestra <cat@gensokyo.uk>

internal/pipewire/pipewire_test.go

@@ -845,6 +845,7 @@ func TestContextErrors(t *testing.T) {
 		{"RoundtripUnexpectedEOFError ErrRoundtripEOFFooter", pipewire.ErrRoundtripEOFFooter, "unexpected EOF establishing message footer bounds"},
 		{"RoundtripUnexpectedEOFError ErrRoundtripEOFFooterOpcode", pipewire.ErrRoundtripEOFFooterOpcode, "unexpected EOF decoding message footer opcode"},
 		{"RoundtripUnexpectedEOFError invalid", pipewire.RoundtripUnexpectedEOFError(0xbad), "unexpected EOF"},
+		{"InconsistentFilesError", &pipewire.InconsistentFilesError{0, 2}, "queued 0 files instead of the expected 2"},
 
 		{"UnsupportedOpcodeError", &pipewire.UnsupportedOpcodeError{
 			Opcode:    0xff,
@@ -855,6 +856,11 @@ func TestContextErrors(t *testing.T) {
 			Id:   -1,
 			Data: "\x00",
 		}, "unknown proxy id -1"},
+
+		{"InvalidPingError", &pipewire.InvalidPingError{
+			ID:       0xbad,
+			Sequence: 0xcafe,
+		}, "received Core::Ping seq 51966 targeting unknown proxy id 2989"},
 	}
 	for _, tc := range testCases {
 		t.Run(tc.name, func(t *testing.T) {