Modernization

removed gitter link

- use standard mapping of Microsoft.Extensions.Logging
- to Serilog (via SerilogLoggerFactory) from Serilog.Extensions.Logging
- tested outputting log messages at INF level ok

- to <TrimMode>full</TrimMode> by default
- add <TrimMode>partial</TrimMode> to get old net5.0 / net6.0 behaviour
- and <SuppressTrimAnalysisWarnings>true</SuppressTrimAnalysisWarnings>
- to only suppress IL2104 warnings
- e.g. error IL2104: Assembly 'Autofac' produced trim warnings
- which otherwise would be treated as errors
- as we set <TreatWarningsAsErrors>true</TreatWarningsAsErrors>
- see: https://stackoverflow.com/questions/74151256/c-sharp-publishtrimmed-how-to-deal-with-il2104-trim-warnings-in-dependencies
- "you can suppress these warnings, but essentially, ..
- there's no way for you to solve the problem".

- handle duplicate keys
- by dropping subsequent items with same key

…e-nupkgs-and-remove-custom-serilog-logger

Upgrades Piggy to `net7.0`, updates all `.nupkg`s to latest, and removes custom Npgsql to Serilog logging bridge...
- Upgrades Piggy to net7.0.
- Updates all .nupkgs to latest.
- Removes custom Npgsql to Serilog logging bridge.
- Rather, uses Microsoft.Extensions.Logging bridge via NpgsqlLoggingConfiguration.InitializeLogging(new SerilogLoggerFactory());
- Because we already use /p:PublishTrimmed=true, we have to set TrimMode=partial and SuppressTrimAnalysisWarnings=true to get back to the net5.0 and net6.0 behaviour.
- This is because net7.0 now defaults to "trim everything that doesn't explicitly opt-out of trimming" where as net6.0 and earlier defaulted to "trim only things that have explicitly opted-in to trimming.
- Also, fixes a bug (applies to datalust.co) where Piggy reports it's connecting to host=null, which obviously isn't true.

…-branches

#2 try to get the builds working with updated scripts

Attempts to fix NuGet.org publish.

- Updates the encrypted NuGet.org deployment API key.
- Removes "dev" deployment of packages to GitHub, as we don't currently (and don't want to) deploy prerelease packages to GitHub.

@nblumhardt has reviewed (over my shoulder) and approved this to be merged.

upgrades "npgsql" to version 7.0.4

- dotnet list package --vulnerable --include-transitive
- reports on vulnerable packages including deps dependencies recursively
- dotnet list package --deprecated --include-transitive
- dotnet list package --outdated --include-transitive
- adjust exit codes to make them sequential

…rable--include-transitive-etc-reporting-only

Add useful `dotnet list package` calls to Build.ps1 to report on NuGet package issues...

- it's not something we can fix
- as it's up to our upstream packages to fix these
- and we can run this explicitly locally if we care to

…clude-transitive

removes --include-transitive as it's noisy and...

Bumps [npgsql](https://github.com/npgsql/npgsql) from 7.0.4 to 8.0.3.
- [Release notes](https://github.com/npgsql/npgsql/releases)
- [Commits](npgsql/npgsql@v7.0.4...v8.0.3)

---
updated-dependencies:
- dependency-name: npgsql
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <support@github.com>

…ggy/npgsql-8.0.3

Bump npgsql from 7.0.4 to 8.0.3 in /src/Datalust.Piggy

…eaks package binary compatibility with varying Npgsql versions

Update to .NET 8 and new Npgsql version

…refix during build

Package and publish as a `dotnet tool` package

Fix dotnet tool publishing

… tricks

Still no luck getting the tool package working; pulling out some more tricks