Upgrade packages flagged in Dependabot alerts

[rhigman]

No description provided.

[rhigman]

• Alerts 21 and 5 are blocked on release of failure >0.1.8.
• Alert 23 is blocked on release of chrono >0.4.19.
• Alert 1 requires a full upgrade to yew 0.19.3, which removes anymap dependency. This will partly be fixed by Upgrade yew to v0.19.3 (including yew-router upgrade to v0.16.0) #397, but yewtil 0.4.0 (the latest version) retains the yew 0.18.0 (and therefore anymap) dependency. This is therefore blocked on release of either yewtil >0.4.0 or anymap >0.12.1.
• Alerts 24, 15 and 14 are blocked by wasm-pack's use of reqwest 0.9 which uses hyper 0.12 (still the case in the latest wasm-pack, 0.10.3).
• Alert 7 is also blocked by the above, as hyper 0.12 uses tokio 0.1.
• Alert 4 is also blocked by the above, as reqwest 0.9 uses tokio-threadpool 0.1 which uses crossbeam-utils 0.7.
• Alerts 8, 9, 10, 11 and 12 are also blocked by the above, as wasm-pack 0.9 and 0.10 use parking_lot 0.6 which uses lock_api 0.1. They are additionally blocked by diesel's use of r2d2 0.8 which uses parking_lot 0.10 which uses lock_api 0.3 (a release candidate for diesel 2.0 is available but this has the same dependency chain).

[rhigman]

Alert 23 has been withdrawn.
Alert 31 is blocked on release of owning_ref >0.4.1. The package is only used by lock_api 0.1.5, so this is another issue which is blocked by wasm-pack dependencies, as above.
Alerts 27, 28, 29, 30 require upgrading to juniper 0.15.10. We are currently on 0.14.2 and there will be some breaking changes. Tracked at #457.

[ja573]

Most have now been closed with #509

Ignoring yew/wasm alerts as they will be dropped with the GUI redesign, the only alert left is related to chrono's dependency on time, which will be dropped in the next version