Published JAR is missing manifest entries

Affects `v2.0.7` (checked), probably earlier as well.

Downloaded the JAR form both GH packages and Maven central. The manifest contains

```
Manifest-Version: 1.0
Archiver-Version: Plexus Archiver
Created-By: Apache Maven 3.8.3
Built-By: hansolo
Build-Jdk: 11.0.13
```

However if the project is build locally you get something similar to

```
Manifest-Version: 1.0
Bnd-LastModified: 1636552490395
Build-Date: 2021-11-10
Build-Revision: a1e766284a1369a742247590273cb1a45684bf97
Build-Time: 14:54:47.561+0100
Built-By: aalmiray
Bundle-Description: Assembles a bundle containing the main classes.
Bundle-License: https://www.apache.org/licenses/LICENSE-2.0;descriptio
n=Apache License Version 2.0;link=https://spdx.org/licenses/Apache-2.
0.html
Bundle-ManifestVersion: 2
Bundle-Name: discoclient
Bundle-SymbolicName: io.foojay.api.discoclient
Bundle-Version: 2.0.7
Created-By: 11.0.11 (Azul Systems, Inc.)
Export-Package: io.foojay.api.discoclient;uses:="io.foojay.api.discocl
ient.event,io.foojay.api.discoclient.pkg,io.foojay.api.discoclient.ut
il";version="2.0.7",io.foojay.api.discoclient.event;version="2.0.7",i
o.foojay.api.discoclient.pkg;uses:="io.foojay.api.discoclient.util";v
ersion="2.0.7",io.foojay.api.discoclient.util;uses:="io.foojay.api.di
scoclient.pkg";version="2.0.7"
Implementation-Title: discoclient
Implementation-Version: 2.0.7
Import-Package: com.google.gson;version="[2.8,3)",io.foojay.api.discoc
lient,io.foojay.api.discoclient.event,io.foojay.api.discoclient.pkg,i
o.foojay.api.discoclient.util,java.io,java.lang,java.lang.invoke,java
.net,java.net.http,java.nio,java.nio.channels,java.nio.charset,java.n
io.file,java.security,java.time,java.util,java.util.concurrent,java.u
til.concurrent.atomic,java.util.function,java.util.regex,java.util.st
ream
Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=11))"
Specification-Title: discoclient
Specification-Version: 2.0.7
Tool: Bnd-5.3.0.202102221516
```

Compare the manifest in the v2.0.7 JARs from GitHub Packages and Maven Central with the manifest produced by a local build. Start by inspecting the project’s packaging and release configuration; done means the published JAR contains the expected manifest entries rather than only the Maven archiver metadata.

Written by the indexing model from the issue text.