Bump gradle-maven-publish-plugin from 0.15.0 to 0.15.1 (#2252)

Summary:
Bumps [gradle-maven-publish-plugin](https://github.com/vanniktech/gradle-maven-publish-plugin) from 0.15.0 to 0.15.1.
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/releases">gradle-maven-publish-plugin's releases</a>.</em></p>
<blockquote>
<h2>0.15.1</h2>
<p><a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md#version-0151-2021-05-02">Changelog</a></p>
</blockquote>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/blob/master/CHANGELOG.md">gradle-maven-publish-plugin's changelog</a>.</em></p>
<blockquote>
<h2>Version 0.15.1 <em>(2021-05-02)</em></h2>
<ul>
<li>The <code>closeAndReleaseRepository</code> task was mistakenly expecting the wrong Gradle properties. The README and changelog also mentioned the wrong properties. The correct ones are <code>mavenCentralUsername</code> and <code>mavenCentralPassword</code> or for environment variables: <code>ORG_GRADLE_PROJECT_mavenCentralUsername</code> and <code>ORG_GRADLE_PROJECT_mavenCentralPassword</code>.</li>
<li>Fix <code>signing</code> not being configurable until <code>afterEvaluate</code></li>
<li>Use empty string as in memory signing password when no password is specified</li>
<li>Fix <code>statingProfile</code> in <code>nexusOptions</code> not being optional which causes an error when running <code>closeAndReleaseRepository</code></li>
</ul>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="c7d73702af"><code>c7d7370</code></a> Prepare version 0.15.1</li>
<li><a href="8a3363016a"><code>8a33630</code></a> apply Signing plugin early in regular plugin (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/235">https://github.com/facebook/flipper/issues/235</a>)</li>
<li><a href="0c677fee10"><code>0c677fe</code></a> make stagingProfile optional (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/236">https://github.com/facebook/flipper/issues/236</a>)</li>
<li><a href="7d9a7b15df"><code>7d9a7b1</code></a> Use mavenCentralUsername and mavenCentralPassword everywhere (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/230">https://github.com/facebook/flipper/issues/230</a>)</li>
<li><a href="cafe2fd0d8"><code>cafe2fd</code></a> Fallback to an empty string when signingInMemoryKeyPassword is null (<a href="https://github-redirect.dependabot.com/vanniktech/gradle-maven-publish-plugin/issues/231">https://github.com/facebook/flipper/issues/231</a>)</li>
<li><a href="d4dfbbcb4c"><code>d4dfbbc</code></a> Update CHANGELOG.md</li>
<li><a href="d2e035c65b"><code>d2e035c</code></a> Prepare next development version.</li>
<li>See full diff in <a href="https://github.com/vanniktech/gradle-maven-publish-plugin/compare/0.15.0...0.15.1">compare view</a></li>
</ul>
</details>
<br />

[![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.vanniktech:gradle-maven-publish-plugin&package-manager=gradle&previous-version=0.15.0&new-version=0.15.1)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `dependabot rebase`.

[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)

 ---

<details>
<summary>Dependabot commands and options</summary>
<br />

You can trigger Dependabot actions by commenting on this PR:
- `dependabot rebase` will rebase this PR
- `dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `dependabot merge` will merge this PR after your CI passes on it
- `dependabot squash and merge` will squash and merge this PR after your CI passes on it
- `dependabot cancel merge` will cancel a previously requested merge and block automerging
- `dependabot reopen` will reopen this PR if it is closed
- `dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
- `dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

</details>

Pull Request resolved: https://github.com/facebook/flipper/pull/2252

Reviewed By: mweststrate

Differential Revision: D28181978

Pulled By: passy

fbshipit-source-id: 2fa5399165a5fd9fb1115ab918170188e616c8e1

build.gradle

@@ -12,7 +12,7 @@ buildscript {
     }
     dependencies {
         classpath 'com.android.tools.build:gradle:4.1.3'
-        classpath 'com.vanniktech:gradle-maven-publish-plugin:0.15.0'
+        classpath 'com.vanniktech:gradle-maven-publish-plugin:0.15.1'
         classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$KOTLIN_VERSION"
         classpath "org.jetbrains.dokka:dokka-gradle-plugin:1.4.32"
     }