base: Closing channel without problem does not close immediately

When closing a channel we send a request to bridge to close the
channel. However we also short circuit the close, so that we aren't
waiting for an unresponsive bridge.

This short circuit shouldn't happen when the channel is closed without
a problem.

Closing a channel without a problem is used to indicate end-of-input
to channels like 'stream'.

Closes #1506
Reviewed-by: Marius Vollmer <marius.vollmer@redhat.com>
man: Update and fix bug reporting links in man pages

Reviewed-by: Marius Vollmer <marius.vollmer@redhat.com>
man: Remove authors sections of man pages

Although Cockpit owes David Zeuthen a lot, it would be incorrect
to describe him as the current author of either of these programs
given the small amount of original code remaining.

Lets just leave these out, its confusing.

Closes #1501
Reviewed-by: Marius Vollmer <marius.vollmer@redhat.com>
tools: Use package.json to identify which nodejs deps to install

Fixes #1498
Closes #1502
Reviewed-by: Marius Vollmer <marius.vollmer@redhat.com>
base: Make it easier to use proxies without CamelCase

 * Support proxy.call(name, args)
 * Support a "signal" event on proxies to catch any signal

Together with the 'data' field already on proxies, this makes it
possible to use proxies without CamelCase properties, methods, signals.
It's slightly less convenient but works well.

In addition this allows calling methods on proxies that are still loading.

Fixes #1500
Closes #1503
Reviewed-by: Marius Vollmer <marius.vollmer@redhat.com>
base: Fix null dereference when qualifying module path

This happens because resolve_path_dots() can return null for
invalid paths.

Closes #1504
Reviewed-by: Marius Vollmer <marius.vollmer@redhat.com>
bridge: Add fsread1, fswrite1, and fswatch1 payload types.