New WebUI: Update angular and angular-route and add workaround to be compatible

[kripton]

This PR updates angular and angular-route to the latest upstream releases (v1.8.3). However, without changes to our new Web UI, this causes it to break as described in #1782. To fix this, a workaround has been added to restore angular's previous behaviour. See https://docs.angularjs.org/guide/migration#commit-aa077e8

As a bonus, the list of dependencies in javascript/new-src/package.json is not sorted alphabetically as is done automatically when adding or updating packages listed therein.

This PR also updates the "built" app.min.js and related files.

[kripton]

Oh, forgot: This PR also updates jQuery to the latest upstream release.

I did test the new Web UI after the changes:

• Navigating
• Changing values via faders
• Changing values via keypad
• Adding a new universe
• Changing universe patching
• Disabling and Re-enabling a plugin
• Requesting plugin reload

All functions seem to work as before

[FloEdelmann]

Oops, sorry

[FloEdelmann]

The code changes look fine. I haven't checked out the code locally though.

[FloEdelmann]

Looks like the Travis CI job doesn't even start. Should we merge the PR manually without that check?

[daveol]

Code changes seem fine, Haven't tested it in the real world though.

[daveol]

Travis CI is giving the following error on the site (when i logged in at least):

    We are unable to start your build at this time. 
    You exceeded the number of users allowed for your plan.
    Please review your plan details and follow the steps to resolution.

[peternewman]

As with others LGTM but I've not tried it.

Just the one possible comment improvement.

[peternewman]

I think we could also add a note saying given this webpage is only used internally, there is no benefit in the web crawler changes.

We could possibly add a TODO to update our URLs to remove this change, but maybe that's not necessary if we're rewriting to a new framework in future?

[kripton]

I agree that this might be useful but since AngularJS (= 1.x) is a dead end, we won't bother for now

[peternewman]

Looks like the Travis CI job doesn't even start.

Travis CI is giving the following error on the site (when i logged in at least):

    We are unable to start your build at this time. 
    You exceeded the number of users allowed for your plan.
    Please review your plan details and follow the steps to resolution.

See e.g. https://travis-ci.community/t/false-statement-builds-have-been-temporarily-disabled-for-private-and-public-repositories-due-to-a-negative-credit-balance/13557/4

You could try going here @kripton and logging into Travis:
https://app.travis-ci.com/organizations/OpenLightingProject/plan/usage

Maybe this is just a guerrilla attempt to force more people to GitHub Actions?

Maybe we should work on this for Linux too:
#1809

Should we merge the PR manually without that check?

Quite possibly, the tests won't really check it aside from the JS linting stuff which I guess you've run?

Or do a dummy commit and see if it does anything the second time around.

[DaAwesomeP]

@peternewman I'm happy to work on a Linux build for GitHub Actions to compliment #1809 and #1812 to fully replace Travis.

[kripton]

You could try going here @kripton and logging into Travis: https://app.travis-ci.com/organizations/OpenLightingProject/plan/usage

I did. It gave me some "plan exceeded" limit, mainly regarding the "number of users on the plan". However, I am unsure if it meant my personal GitHub account or the OpenLightingProject organization.
I would also say let's try to get rid of Travis and do everything with GH Actions. @DaAwesomeP: Thanks for picking it up!

With all the positive review feedbacks here and since Travis won't catch errors in JavaScript anyways, I'll just merge this one.