Correcting API documentation of builds vs. allBuilds

[jglick]

See #1817 (comment).

Testing done

jenkins/core/src/main/java/hudson/model/Job.java

Lines 784 to 787 in 75410bc

	@Exported(name = "builds")
	public RunList<RunT> getNewBuilds() {
	return getBuilds().limit(100);
	}

remains the current value. Not tested other than that.

Proposed changelog entries

• N/A

Proposed upgrade guidelines

N/A

Desired reviewers

@daniel-beck

Before the changes are marked as ready-for-merge:

Maintainer checklist

Preview Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
6. If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[A1exKH]

LGTM.