Restarting media session when ICE fails has been working well for some time now.

It doesn't get translated in the TS build, for one.

Script I used:

```python
import os

for (dirpath, dirnames, filenames) in os.walk('.'):
    if '.git' in dirpath:
        continue
    if 'node_modules' in dirpath:
        continue
    if 'dist' in dirpath:
        continue
    if 'types' in dirpath:
        continue
    for filename in filenames:
        path = os.path.join(dirpath, filename)
        if not path.endswith('.js') and not path.endswith('.ts'):
            continue
        #print(path)
        with open(path, 'r+') as f:
            #print(f)
            data = f.read()
            if '__filename' in data:
                p, ext = os.path.splitext(path)
                txt = f"'{p[2:]}'"
                print(txt)
                data = data.replace('__filename', txt)  # Assign the result back to data
                f.seek(0)
                f.write(data)
                f.truncate()
```

This makes sure that any track operations that are executed after the terminate is sent and before the new session is established get synced up on the new session.
Also reset the JVB stats. Fixes https://github.com/jitsi/jitsi-meet/issues/14326.

Fixes issue #1476
Alternative to PR #1487

Force the client to reload when the bridge that is handling the media goes down.
This mitigates issues seen on the bridge because of a client re-joining the call with the same endpointId, BWE issues, etc.
This behavior is configurable through 'enableForcedReload' setting in config.js.

If ICE fails will set the special request restart attribute
in the 'session-terminate' sent to Jicofo in order to restart
the Jingle session.

Simplifies the logic for delayed ICE failed event by relying
on XMPP ping instead of the networkInfo module to check
if the internet is online.

There's a plan for using ping to detect XMPP WebSocket
disconnected instead of waiting for timeouts on the network layer.

This also simplifies ICE failed handling logic.

Adds extra 15 seconds before emitting ICE failed event. If the OS is capable of
reporting internet offline status then will start counting when the internet
comes back online.

The reason for that is when ICE restarts are disabled a user will get the page reload
screen immediately, but there's a chance to recover as long as the channels have not
expired on the bridge.