Bumps the dependencies group with 2 updates: [io.avaje:avaje-inject](https://github.com/avaje/avaje-inject) and io.avaje:avaje-inject-generator.


Updates `io.avaje:avaje-inject` from 11.2 to 11.3
- [Release notes](https://github.com/avaje/avaje-inject/releases)
- [Commits](avaje/avaje-inject@11.2...11.3)

Updates `io.avaje:avaje-inject-generator` from 11.2 to 11.3

---
updated-dependencies:
- dependency-name: io.avaje:avaje-inject
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
- dependency-name: io.avaje:avaje-inject-generator
  dependency-type: direct:production
  update-type: version-update:semver-minor
  dependency-group: dependencies
...

Signed-off-by: dependabot[bot] <[email protected]>

…-6a5e79467e

Bump the dependencies group with 2 updates

The JAXB collections don't have setters but instead lazy initialise collections on getter methods, the generated code uses <getter>.addAll() which doesn't support the case when NULL is returned (vs empty collection).

Fix is to add a nullToEmpty() helper method for this case (JAXB style collections).

…pplier

Fix in DJsonb by adding `.nullSafe()` for the `Supplier<JsonAdapter<T>>` case.

Fix NPE when custom JsonAdapter (not nullSafe()) is registered via Supplier

It seems passing a null map/list for serialization throws an NPE

Collection adapter nullsafety

remove unused adapters

- Default to allowing NULL for primitives like Jackson
- Add failOnNullPrimitives=true configuration option

…ption

Add failOnNullPrimitives option, default to allowing NULL