Pin to 3.1.0 maven-gpg-plugin in deploy script [skip ci]

[NvTimLiu]

To fix: #10624

As latest maven-gpg-plugin has the issue "error 401 Unauthorized"

when deploy files onto Sonatype repo, we pin it to the

stable version 3.1.0 to unblock our release process.

[NvTimLiu]

3.1.0 maven-gpg-plugin has the same "401 Unauthorized" now.

Draft this PR until we maven-gpg-plugin fixed the issue, or we need a work around for deploy.

[NvTimLiu]

3.1.0 maven-gpg-plugin has the same "401 Unauthorized" now.

Draft this PR until we maven-gpg-plugin fixed the issue, or we need a work around for deploy.

Seems like maven-gpg-plugin:3.1.0 or its dependency jars had intermittent errors, but now it works again!

[sameerz]

3.1.0 maven-gpg-plugin has the same "401 Unauthorized" now.
Draft this PR until we maven-gpg-plugin fixed the issue, or we need a work around for deploy.

Seems like maven-gpg-plugin:3.1.0 or its dependency jars had intermittent errors, but now it works again!

Is this PR still required?

[NvTimLiu]

3.1.0 maven-gpg-plugin has the same "401 Unauthorized" now.
Draft this PR until we maven-gpg-plugin fixed the issue, or we need a work around for deploy.

Seems like maven-gpg-plugin:3.1.0 or its dependency jars had intermittent errors, but now it works again!

Is this PR still required?

@sameerz Yes this PR is still required.

Just checked Sonaytpe status, the intermittent 401 for 3.1.0 problem was from maven-gpg-plugin:3.1.0, but from SONATYPE itself, as not any maven-gpg-plugin version worked that day(but resumed later the second day). Sonatype Incident

So 3.1.0 of maven-gpg-plugin is still stable!

We should use the 3.1.0 as the stable fixed version in our deploy script instead of always use the latest version, until dependency/compatible issue appears(maybe due to integration of many new versions later), as we're not sure whether latest version has any issue or not.

[sameerz]

build