* feat(base/conference): fixed getting localSubject, subject and parsing url params.

- `getPropertyValue` calls `parseUrlParam` with the connection URL from store, which is not yet defined

Remove unnecessary @ts-ignores
Use @ts-expect-error instead of @ts-ignore for external dependencies

Fix some errors. Remove @ts-ignores
Convert some files to TS
Remove some eslint-disables

Use new TS config from @jitsi/eslint
Fix all lint errors

After https://github.com/jitsi/jitsi-meet/pull/11607 we might call it
with a string. Be nice and accept that in addition to URL objects.

Web's ExternalAPI accepts an object with properties as one of its
constructor arguments and from which it generated a URL. Mobile's
JitsiMeetView.loadURLObject is supposed to accept pretty much the same
object.

The counterpart of the external API in the Jitsi Meet Web app uses the
search URL param jwt to heuristically detect that the Web app is very
likely embedded (as an iframe) and, consequently, needs to forcefully
enable itself. It was looking at whether there was a JSON Web Token
(JWT) but that logic got broken when the JWT support was rewritten
because the check started happening before the search URL param jwt was
parsed.

Make 'Add jwt module to react' work on mobile.