Download JAR files tagged by slf4j with all dependencies

A tool for data backup and consistency. Architecture and technologies: + the classic three-tier architecture is used: Model, DAO, Presentation; + [Spring 6 / Spring Boot 3](https://spring.io/) is the reference framework; + [SQLite](https://sqlite.org/) is the underlying database; + [Spring Data JPA](https://docs.spring.io/spring-data/jpa/docs/current/reference/html/) with [Hibernate](https://hibernate.org/) is used as ORM; + JPA entities are separated objects; + `Finder` and DCI roles from [TheseFoolishThings](http://tidalwave.it/projects/thesefoolishthings) are used; + [SLF4J](https://slf4j.org) and [Logback](https://logback.qos.ch) are used for logging; + [TestNG](https://testng.org) and [Mockito](https://site.mockito.org/) are used for testing; + [Lombok](https://projectlombok.org) is used for cleaner code.

This module groups all different output writers. Different output writers have different dependencies. To ensure that those dependencies do not leak to other output writer, or that we can limit to number of dependencies at runtime, output writers are split into separate modules based on the dependencies they use. For example, the CloudWatch output writers depends on the AWS SDK, which is quite large and not used by any other output writer. If you only want to send metrics to Graphite, there should be no need to have the AWS SDK in your classpath at runtime. Some dependencies are also problematic. They can introduce incompatibilities. For example, a few writers are based directly on log4j or logback. This direct dependence breaks the use of SLF4J. By isolating those output writers to a specific module, we can ensure this has minimal impact.