Udata

- [BREAKING] Remove metrics computation with Matomo as a source (cf below) [273](https://github.com/opendatateam/udata-piwik/pull/273)
- Replace mongo legacy image in CI [266](https://github.com/opendatateam/udata-piwik/pull/266)
- Upgrade test and develop deps [284](https://github.com/opendatateam/udata-piwik/pull/284)

Up until this version, metrics were tentatively computed from Matomo for pretty much every object of a udata instance. We found this method to be pretty inaccurate, since Matomo limits the number of records stored to roughly the most visited 1000 for a given "namespace". There's a way around that by using the data from the Live module of Matomo but it's not enabled on our instance for privacy reasons. We also needed to count hits that Matomo could not know of: resources (files) downloads made directly on our server.

Thus, this module now only does three things:
- inject the Matomo tracking code in the templates
- process events for tracking the API usage in Matomo
- process events for tracking some Matomo goals

Metrics computation is now handled by [https://github.com/opendatateam/udata-metrics](udata-metrics) and does not use Matomo as a source.

:warning: Jobs to be unscheduled:
- `piwik-update-metrics`
- `piwik-current-metrics`
- `piwik-yesterday-metrics`

- Extend dcat properties support (frequency litteral, creation and modification date, landing page and abstract description) [2715](https://github.com/opendatateam/udata/pull/2715)

- **Deprecation**: Topics are now deprecated and will be removed in upcoming releases.
- Use title to improve License guess [2697](https://github.com/opendatateam/udata/pull/2697)
- Add a `q` argument to the paginated datasets resources endpoint, to search through resources titles. [2701](https://github.com/opendatateam/udata/pull/2701)
- Delete discussion with deleted user as only participant [2702](https://github.com/opendatateam/udata/pull/2702)
- Fix error on post creation when adding related reuse [2704](https://github.com/opendatateam/udata/pull/2704)
- Redirect in endpoints routing now returns 308 instead of 302 in order to keep the method and body. [2706](https://github.com/opendatateam/udata/pull/2706)
- Delete badges from datasets fixtures. [2709](https://github.com/opendatateam/udata/pull/2709)

- Fix fields empty value in admin form to allow for unsetting fields [2691](https://github.com/opendatateam/udata/pull/2691)
- :warning: Add a new required topic string field on reuses. The associated migration set default topic to `others` [2689](https://github.com/opendatateam/udata/pull/2689)

- :warning: Removed `Issues` code and logic. The corresponding MongoDB collection should be deleted when upgrading Udata. [2681](https://github.com/opendatateam/udata/pull/2681)
- Fix transfer ownership from org to user [2678](https://github.com/opendatateam/udata/pull/2678)
- Fix discussion creation on posts [2687](https://github.com/opendatateam/udata/pull/2687)

- Move template hook logic back to udata [2671](https://github.com/opendatateam/udata/pull/2671) [#2679](https://github.com/opendatateam/udata/pull/2679)
- Add dataset's acronym to catalog [2675](https://github.com/opendatateam/udata/pull/2675)
- Better URL-based License guess [2672](https://github.com/opendatateam/udata/pull/2672)
- New way of fixtures generation [2677](https://github.com/opendatateam/udata/pull/2677):
- The command now uses a remote file (default) if a URL is provided or a local one if a path is provided.
- This file can be generated by using the command `generate-fixtures-file`, which takes as an argument the URL of the source queried to retieve the data dumped to the file.
- The command `generate-fixtures-file` uses a customizable list of datasets slugs to know which datasets to query.
- Fixed the Geomform check for a GeoZone instance in formdata [2683](https://github.com/opendatateam/udata/pull/2683)