GitLab

feat: block on trim

Co-Authored-By: Raúl Kripalani <raul@protocol.ai>

Bump github.com/multiformats/go-multiaddr from 0.1.2 to 0.2.0

Pro: It's a lot simpler.
Con: We lose the ordering guarantee. Before, TrimOpenConns would only return
     once a trim that started _after_ calling TrimOpenConns finished. Now, it
     returns as soon as it observes _any_ trim finishing (even if the trim
     started earlier).

Bumps [github.com/multiformats/go-multiaddr](https://github.com/multiformats/go-multiaddr) from 0.1.2 to 0.2.0.
- [Release notes](https://github.com/multiformats/go-multiaddr/releases)
- [Commits](https://github.com/multiformats/go-multiaddr/compare/v0.1.2...v0.2.0)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

1. Perform all trims in the background goroutine.
2. Make `TrimOpenConns` return early when canceled.
3. Make multiple concurrent calls to `TrimOpenConns` block until the trim
   finishes. Note: It already _may_ block one caller, this just ensures that it
   always behaves the same way.

Returning a signal channel may be a nicer solution but this is less breaking.

Bump github.com/multiformats/go-multiaddr from 0.0.2 to 0.1.2

Bumps [github.com/multiformats/go-multiaddr](https://github.com/multiformats/go-multiaddr) from 0.0.2 to 0.1.2.
- [Release notes](https://github.com/multiformats/go-multiaddr/releases)
- [Commits](https://github.com/multiformats/go-multiaddr/compare/v0.0.2...v0.1.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bump github.com/libp2p/go-libp2p-core from 0.0.1 to 0.2.5

Bumps [github.com/libp2p/go-libp2p-core](https://github.com/libp2p/go-libp2p-core) from 0.0.1 to 0.2.5.
- [Release notes](https://github.com/libp2p/go-libp2p-core/releases)
- [Commits](https://github.com/libp2p/go-libp2p-core/compare/v0.0.1...v0.2.5)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

don't count connections in the grace period against the limit

fixes #46

Background trimming

otherwise the target can be 0, which makes it negative on decrement, and it will end up
dropping all connections.

- fix potential concurrent modification of connection map
  from concurrent connects/disconnects by locking the segment
- don't spawn goroutines on every connect during trims

Implement UpsertTag

Add peer protection capability (implementation)