build(deps): bump elliptic from 6.4.0 to 6.5.3 in /client

Bumps [elliptic](https://github.com/indutny/elliptic) from 6.4.0 to 6.5.3.
- [Release notes](https://github.com/indutny/elliptic/releases)
- [Commits](https://github.com/indutny/elliptic/compare/v6.4.0...v6.5.3

)
Signed-off-by: dependabot[bot] <support@github.com>

build(deps): bump lodash from 4.17.15 to 4.17.19 in /client

Bumps [lodash](https://github.com/lodash/lodash) from 4.17.15 to 4.17.19.
- [Release notes](https://github.com/lodash/lodash/releases)
- [Commits](https://github.com/lodash/lodash/compare/4.17.15...4.17.19

)
Signed-off-by: dependabot[bot] <support@github.com>

billing: cope with spy-interval set longer than publish-interval

improvement: stop rendering if Context is cancelled

Typically this means the http caller has closed the connection,
so no point responding to them.

Also check at the point we send a response back, and log to OpenTracing.

fix (integration tests): replace localhost with 127.0.0.1 

Update to most recent weaveworks/ui-components

	As this would have deleted some headers in
	./vendor/github.com/iovisor/gobpf/elf
	I also ran
	git diff vendor/github.com/iovisor/gobpf/ | patch -p0 -R

multitenant query: don't drop topologies so much

Where a report has been merged from several probes, give it a higher
limit before dropping topologies.

We will already have applied the limit on each single-probe report as
it came in, except for historical ones.

Missed earlier.

Update tools: Go 1.4.2 and JS kind-of 6.0.3

Fixed example for PodSecurityPolicy inside examples/k8s/psp.yaml

PodSecurityPolicy (in the extensions/v1beta1 API group)
Migrated to use the policy/v1beta1 API, available since v1.10. Existing persisted data can be retrieved/updated via the policy/v1beta1 API.
Signed-off-by: knrt10 <tripathi.kautilya@gmail.com>

multitenant: scan container command-lines as well as process

Release 1.13.1

Don't quote RELEASE_ARGS which may contain two arguments

Removed kubelet port flag. Node name now always need from env/flag

We should have done this anyway, but I haven't noticed the error
previously. Possibly Go 1.14 is more aggressive about exiting when
some goroutines are still active.

We got a warning about a vulnerability in 6.0.2

Stop pipe operations after EOF

This comes back when an operation like Kubernetes Describe finishes;
hide it so we don't print as an error.

Previously we were treating EOF on the reader as no-error, meaning
that operations like Kubernetes Describe would retry endlessly when
finished.

Upgrade reports before merging in multitenant collector

In case they came from an older or an overload probe.

Need to modify DropTopologiesOver() to report what it dropped, and
plumb through the userid so the metric can show who has a problem.