Add skipPublishDocGithubIo for all Spring starters

[saragluna]

Description

The Spring starters have no Javadocs, so we should stop publishing the empty Javadoc jars to the GitHub IO site. This PR will add the skipPublishDocGithubIo: true to all Spring starters.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[XiaofeiCao]

Hi @saragluna, when will this PR be merged? I'm getting ci error here:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=1592813&view=logs&jobId=7108164a-7e0a-5672-22b4-83801a88006a&j=7108164a-7e0a-5672-22b4-83801a88006a&t=c2ae752a-fb25-5514-4562-48637360b096

Thought this PR would fix this?

[saragluna]

Hi @XiaofeiCao, I checked the pipeline and it's because we are using a README file in sdk/spring folder, but this file is not checked out in the Sparse checkout repositories step. So merging this PR won't fix the issue. Let's see how to address it.

[saragluna]

Hi @XiaofeiCao, I just created this #29013 to fix the issue.

[XiaofeiCao]

Hi @XiaofeiCao, I just created this #29013 to fix the issue.

Thanks!

[JimSuplizio]

Thank you @saragluna. This makes the doc publishing (or lack thereof) consistent.

[JimSuplizio]

Hi @saragluna, when will this PR be merged? I'm getting ci error here: https://dev.azure.com/azure-sdk/public/_build/results?buildId=1592813&view=logs&jobId=7108164a-7e0a-5672-22b4-83801a88006a&j=7108164a-7e0a-5672-22b4-83801a88006a&t=c2ae752a-fb25-5514-4562-48637360b096

Thought this PR would fix this?

@saragluna the problem here is that every library, in theory, is supposed to have a README and that's what should be included in the empty javadoc/sources, not the root README. Spring seems to be an exception to this. I'm looking at changing the sparse checkout paths generated for the FromSource runs to accommodate this but that probably won't be fixed until tomorrow (Tuesday, May 24th).

[saragluna]

@JimSuplizio, we are trying to see whether we could skip the README.md files in Spring empty Javadoc or sources jar files in #29014. The jar files will contain a META-INF folder, which means they are not empty.

[JimSuplizio]

@JimSuplizio, we are trying to see whether we could skip the README.md files in Spring empty Javadoc or sources jar files in #29014. The jar files will contain a META-INF folder, which means they are not empty.

@saragluna there's a reason we're putting the README into the 'empty' sources and javadocs and that's because of explicit instructions for publishing.
If, for some reason (for example, license issue or it's a Scala project), you can not provide -sources.jar or -javadoc.jar , please make fake -sources.jar or -javadoc.jar with simple README inside to pass the checking. We do not want to disable the rules because some people tend to skip it if they have an option and we want to keep the quality of the user experience as high as possible.