Mara-pipelines

Rename package from `data_integration` to `mara_pipelines`.

**required changes**

- In requirements.txt, change `-e git+https://github.com/mara/data-integration.git2.8.3#egg=data-integration` to `-e git+https://github.com/mara/mara-pipelines.git3.0.0#egg=mara-pipelines`
- If you use the `mara-etl-tools` package, update to version `4.0.0`
- In your project code, replace all imports from `data_integration` to `mara_pipelines`
- Adapt navigation and ACL entries, if you have any (their names changed from "Data integration" to "Pipelines")

Here's an example of how that looks at the mara example project 2: https://github.com/mara/mara-example-project-2/commit/fa2fba148e65533f821a70c18bb0c05c37706a83

- Fix duplicated system stats if you run multiple ETLs in parallel (38)
- Add config default_task_max_retries (39)
- Cleaner shutdown (41)

- Ignore not succeeded executions in cost calculation (36)
- Ensure we log errors via events in case of error/shutdown (33)
- Fix a bug where we reported the wrong error to chat channels when running in
the browser and did not restart between failed runs (33)

- Fix Problems when frontend and database are in a different timezone (34)

- Implement pipeline notifications via Microsoft Teams 28
- Make it possible to disable output coloring in command line etl runs (31)

- Make event handlers configurable: this allows for e.g. adding your own notifier for specific events
- Switch slack to use events for notifications of interactive pipeline runs
- Fix an edge case bug where reverting a commit after an error in the table creation for an incremental load
job would not recreate the original tables leading to a failed load
- Fix an edge case bug where crashing during a triggered (code change, TRUNCATE) full load of an
incremental load job after the table was already loaded would not rerun the full load
leading to missing data
- Optimize how we set the spawning method in multiprocessing