Add pagination to management API

- Allows longer length replies from the management API, without stalling
  the core daemon or requiring large amounts of RAM.
- Adds a small change to the published API.  Since the previous API
  would have been broken for large results, no user visible changes in
  functionality are actually happening (Either it was not broken
  previously and it is unchanged now, or it was broken previously and
  will now return a clearer error result now)

This release also contains:
- a bugfix to remove a memory leak
- Some minor CI changes

Add pagination to management API

- Allows longer length replies from the management API, without stalling
  the core daemon or requiring large amounts of RAM.
- Adds a small change to the published API.  Since the previous API
  would have been broken for large results, no user visible changes in
  functionality are actually happening (Either it was not broken
  previously and it is unchanged now, or it was broken previously and
  will now return a clearer error result now)

- Also contains a bugfix to remove a memory leak

TCP mode bug fixes and more

- Improve built dpkg version numbers
- Clearly show API buffer overflows
- Allow management unix sock to have different perms
- Continue improving the unstable /metrics endpoint
- Keep metrics of time spent waiting for name resolution

Bugs fixed:
- Fix a couple of bugs in TCP socket disconnect/reconnect handling
- Fix some DEL_P2P event reporting

Federation bug fixes

Some issues were found with multiple federated supernodes and how they
handled edges moving between them.

These issues would result in occasional loss of connectivity between
edges connected via different supernodes.

- Federated MAC addresses would regularly be timed out and deleted due to a
  faulty "last_seen" update.
- Federated supernodes would have trouble registering due to a bad boolean
  conversion.
- Some additional refactoring and monitoring was also added while tracking
  these down.

Functionally identical to 3.3.0

The 3.3.1 tag used github actions automation with errors in it and did
not complete successfully.

Functionally identical to 3.3.0

The merge and the tag were done in the wrong order for the 3.3.0 release
to correctly drive the automation, so this point release is doing it
again.

First release of the new n3n project

Major improvements since the fork from n2n:

- Documentation
- Command line processing simplification
- Configuration file loading
- JsonRPC API with built-in web server
- Significantly improved Debian and Redhat packaging
- More automated tests and builds

moved dev to version 3.1.1

Start of 3.1 dev