feat: remote peertube servers list

[shpingalet007]

Standards checklist:

• [x] The PR title is descriptive.
• [x] The PR doesn't replicate another PR which is already open.
• [x] The PR has self-explained commits history.
• [x] The code is mine, or it's from somewhere with an Apache-2.0 compatible license.
• [ ] The code is efficient, to the best of my ability, and does not waste computer resources.
• [ ] The code is stable, and I have tested it myself, to the best of my abilities.
• [ ] If the code introduces new classes, methods, I provide a valid use case for all of them.

Changes:

• Using remote peertube servers list
• Grunt for Proxy16 build and preparation process

Other comments:

Peertube servers list is packed on build steps. We have offline version packed inside and remote one that is updated on application start.