shell, NM model: Remove unused functions

Namely, refresh_all_devices and refresh_object_properties.

Closes #1532
Reviewed-by: Stef Walter <stefw@redhat.com>
bridge: Add a prepare vfunc to CockpitChannel

The queueing of cockpit_channel_ready() and cockpit_channel_close()
was too magical and causing too much complexity.
bridge: When we receive clean close before ready, don't close yet

When we received data or a clean close before the channel is ready
don't close prematurely. Make sure all the data is drained, and
then do the clean close.
bridge: CockpitChannel "disconnected" when transport closes

The CockpitChannel closes unsuccessfully when the transport
closes. This lets implementations react immediately, even if the
transport closes without error.

Closes #1518
bridge: More robust parsing of channel options

The parsing of channel options was quite haphazard, and didn't
detect bad types for values, etc. This is more verbose, but it's more
failure proof and produces better diagnostic messages.
bridge: Better diagnostics for file read/write failures

In the file read/replace channels, put some context in the messages
so we can have a clue as to what's causing it. Previously we had:

cockpit-bridge-Message: /tmp/.V3DRPX/foo: Bad file descriptor
bridge, ws: An empty "problem" in a "close" message is a problem

A missing "problem" is a success. If the "problem" is present no matter
what it's content, then that denotes a problem.
bridge, base ws: Add the "eof" control message and change "close"

The new "eof" control message indicates the end of data in a channel
in a particular direction. It is relevant together with specific
payloads and affects their behavior. It may only be sent once per
direction, and after that point no more messages may be sent in
that direction.

The "eof" provides handshake interlocking for the success case for
payloads where this is necessary.

There is also no longer a "close" handshake. Either end can "close"
a channel, and the channel is considered closed immediately. In the
case of races, further messages are ignored.
common: Fix uninitialized memory access in CockpitTransport

Closes #1531
base: Implement base64 encoding of binary data

This is a surprising omission from the ArrayBuffer and typed array
work. Very odd.

Implementation is a polyfill from MDN, and fixed up.

https://developer.mozilla.org/en-US/docs/Web/API/WindowBase64/Base64_encoding_and_decoding

Our implementation works with binary data in Array, Uint8Array or
Strings.
base: Implement UTF8 encoding and decoding

We would like to use this with Arrays and not just strings like
decodeURIComponent() do. In addition we would like to stream and
possibly ignore encoding errors. In some browsers TextEncoder
and TextDecoder do some of this, but none of the solutions do
exactly what we need.
docker: A new package for docker stuff
base: More general name for console CSS styles
shell: Give AMD interim module loading its own global

If we hang these off of the shell global, then they start to
conflict with things that are already there.
docker: Add component that shows docker logs or console

And use this component in our main docker container details pages.
In addition document it for use outside of Cockpit.

Closes #1364
shell: Don't poll docker containers and images via REST

Instead watch /var/lib/docker for changes, and use that to augment
the somewhat flakey REST /events stream.

Closes #1520
bridge: Rename old rest-json1 code out of the way
common: Allow skipping bytes after in cockpit_pipe_consume()
bridge: Consistent parsing of address channel options

So we have consistent handling for both stream and the upcoming
http-stream1 channels.
bridge: Allow connecting back to the test-server port in tests

This does implement a general mechanism for addressing internal
things that the bridge knows about, that don't have a stable
port or unix path address. Would like to make more use of this
in the future, but for now just implement the test-server port
as an internal address.