Acknowledge DeviceMute widget actions

[toger5]

This prevents sending the default error response to the widget.
required for: element-hq/element-call#2482

Checklist

• Tests written for new code (and old code if feasible).
• New or updated public/exported symbols have accurate TSDoc documentation.
• Linter and other CI checks pass.
• Sign-off given on the changes (see CONTRIBUTING.md).

[dbkr]

These were just unused?

[toger5]

yes I could not find where they were used in EC, the react sdk and the widget api.

[t3chguy]

They were used by Jitsi.

https://github.com/element-hq/element-web/blob/develop/src/vector/jitsi/index.ts#L197-L206

If they were stale then they should have been removed on that side first

[t3chguy]

Looks like 1f64835 stopped the use of those enum values

[t3chguy]

@robintown as the author of that commit do you have any additional context?

[t3chguy]

Looks like it powered a set of quick controls in the left panel which were removed

[t3chguy]

element-hq/element-web#27858 should fix it

[toger5]

Can we allow this change without test coverage? I don't want to write a test that emits a signal and checks if reply is called? There might be a tiny bit of value in this test in terms of regression prevention but if someone removes this code it most likely is for a reason?

Am I overseeing sth. What are other takes on this?

[t3chguy]

The policy is code either needs Jest coverage or a playwright test up to an 80% mark to match customer contracts. Pick your poison unfortunately

[toger5]

The policy is code either needs Jest coverage or a playwright test up to an 80% mark to match customer contracts. Pick your poison unfortunately

Okay that obviously rules out the "being less strict" approach.
I will write a unit test for it.