Add jsdoc type checking for all of react code

[alansartorio]

Add yarn lint command that runs tsc type checking.
I think this will be helpful to prevent errors when changing stuff.

Some of the stuff I did:

• Add typing for native messages: https://github.com/IceDBorn/pipewire-screenaudio/blob/77a6e5461a8e7f3176570774e6683e8a9053f9cf/extension/react/lib/nativeMessageTypes.d.ts . This will help updating the frontend's code after changing the native API.
• Add typing for every untyped variable.
• Fix issues found after typing. Like removing props that don't exist or are unused.
• Refactor some code to make it easier for tsc to prove. Like separating {isLoading: boolean, data: T | undefined} to {isLoading: true, data: undefined} | {isLoading: false, data: T} so both variables end up being linked.
• Add typing for localstorage

[jim3692]

Great work Alan, but what are the benefits of using JSDoc, instead of switching to Typescript?

[IceDBorn]

I agree with @jim3692, we should use Typescript.

[alansartorio]

I also prefer typescript, it's cleaner for me. I just chose jsdoc because we were already using js, and didn't know if you chose js over ts for a reason.

The only benefits are that we can use it in the background and injector without adding a transpilation step (I only edited react though).

I will do the change to typescript in this same PR.

[jim3692]

There is no need to change everything to TS. The injected code, and other parts that don't have type checking yet, can stay in JS.

There is this option in tsconfig: https://www.typescriptlang.org/tsconfig/allowJs.html

Also, to answer your question, we opted for JS, because we were too lazy to write TS and we didn't see enough benefits on such a simple UI component to go that route.

[alansartorio]

Yeah, I was only gonna change the react part to ts. Are you okay with this change to TS then?

[IceDBorn]

@alansartorio Back then, our scope was not that big either 😛