Upgrade nfpm and set release in config

[kpenfound]

RELTOOL-87

This will include the package release in the package names and metadata.

TODO: test building packages and verify naming

[kpenfound]

Test results:
Before change:

$ docker run -e INPUT_NAME=test -e INPUT_ARCH=amd64 -e INPUT_VERSION=1.0.0-rc1+ent -e INPUT_BINARY=nfpm_rpm_config.yaml -e INPUT_MAINTAINER=test actions-packaging-linux
Creating template files...
Packaging...
using rpm packager...
created package: out/test-1.0.0~rc1+ent.x86_64.rpm
using deb packager...
created package: out/test_1.0.0~rc1+ent_amd64.deb

after change:

$ docker run -e INPUT_NAME=test -e INPUT_ARCH=amd64 -e INPUT_VERSION=1.0.0-rc1+ent -e INPUT_BINARY=nfpm_rpm_config.yaml -e INPUT_MAINTAINER=test actions-packaging-linux
Creating template files...
Packaging...
using rpm packager...
created package: out/test-1.0.0~rc1+ent-1.x86_64.rpm
using deb packager...
created package: out/test_1.0.0~rc1+ent-1_amd64.deb

This looks right to me. Does this look like you expect it to @shore ? (Adding the -1 release)

[shore]

after change:
...
created package: out/test-1.0.0rc1+ent-1.x86_64.rpm
...
created package: out/test_1.0.0rc1+ent-1_amd64.deb

This looks right to me. Does this look like you expect it to @shore ? (Adding the `-1` release)

Looks OK to me. The filenames parse like this:

Fields{
    Arch:           "amd64",
    OS:             "linux",
    Product:        "test",
    Type:           "deb",
    Version:        "1.0.0~rc1+ent",
    PackageRelease: "1",
}
Fields{
    Arch:           "x86_64",
    OS:             "linux",
    Product:        "test",
    Type:           "rpm",
    Version:        "1.0.0~rc1+ent",
    PackageRelease: "1",
}

The releases service still doesn't know what to do with ~ delimiters, so prerelease packages I think still can't be submitted to the service. But the package release part works as expected.

[kpenfound]

Perfect, thanks! Yeah this isn't hoping to address the prerelease notation, just the package release