apply auth and headers in public route, use specific tested handler in all specs, only use credentials in Basic auth tests

…eennodes

# Conflicts:
#	eclair-node/src/main/scala/fr/acinq/eclair/api/Service.scala

…some line breaks

…matting changes, re-added auth header in tests as it can not be isolated in handler chain order.

Since we almost always know which transactions will spend the utxos that we are watching, we can optimize the watcher to look for those instead of starting from scratch.

This fixes the `multiarg infix syntax looks like a tuple and will
be deprecated` warning.

If a channel closes when we've received an UpdateFailHtlc, signed it but
not yet received our peer's revocation, we need to fail the htlc upstream.

That specific scenario was not correctly handled, resulting in upstream
htlcs that were not failed which would force our upstream peer to close
the channel.

When using anchor outputs, the commitment feerate is kept low (<10 sat/byte).
When we need to force-close a channel, we must ensure the commit tx and htlc
txs confirm before a given deadline, so we need to increase their feerates.

This is currently done only once, at broadcast time.
We use CPFP for the commit tx and RBF for the htlc txs.
If publishing fails because we don't have enough utxos available, it will
be retried after the next block is confirmed.

Note that it's still not recommended to activate anchor outputs.
More work needs to be done on this fee bumping logic and utxos management.

This command is sent by the `Peer` to its `PeerConnection`, therefore it
needs to be a `RemoteType` and have its own codec.

* add tests on funding mindepth

We verify that when using wumbo channels:
- if we are funder we keep our regular min_depth
- if we are fundee we use a greater min_depth

* use lenses to simplify tags handling

Co-authored-by: Bastien Teinturier <[email protected]>

The module is still there and can be enabled if needed.

We previously used a Set, which means you could theoretically have a feature
that is both activated as `optional` and `mandatory`.

We change that to be a Map `feature -> support`.

We just merged lightning/bolts@b201efe in the spec
which added Bolt 3 tests, invalidating one of our tests and failing the build.

Drop mention of p2sh-segwit. We should encourage users to use bech32.

# Conflicts:
#	eclair-node/src/main/scala/fr/acinq/eclair/api/serde/JsonSerializers.scala

…api-dsl