Add authentication note to releases API

What does this MR do?

Adds an authentication section to the Releases API to clarify the authentication methods used by these endpoints.

Follow-up from gitlab-runner!3023 (comment 631195282)

Screenshots or Screencasts (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

changed milestone to %14.2

added Stuff that should Just Work Technical Writing devopsrelease [DEPRECATED] documentation grouprelease [DEPRECATED] labels

assigned to @jaime

mentioned in merge request gitlab-runner!3023 (merged)

	1 Message
	This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

Documentation review

The following files require a review from a technical writer:

• doc/api/releases/index.md

The review does not need to block merging this merge request. See the:

• Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
• The Technical Writer assigned for that stage and group.
• Documentation workflows for information on when to assign a merge request for review.

If needed, you can retry the danger-review job that generated this comment.

Generated by Danger

added docsimprovement twdoing labels

requested review from @eread

resolved all threads

added 1 commit

• 4fc8783b - Apply 1 suggestion(s) to 1 file(s)

Compare with previous version

approved this merge request

@eread, thanks for approving this merge request.

Please consider starting a new pipeline if:

• This is the first time the merge request is approved, or
• The merge request is ready to be merged, and there has not been a merge request pipeline in the last 2 hours.

For more info, refer to the guideline.

resolved all threads

enabled an automatic merge when the pipeline for 8814f9dd succeeds

merged

mentioned in commit fc757f9a

added workflowstaging label

added workflowcanary label and removed workflowstaging label

added workflowproduction label and removed workflowcanary label

added releasedcandidate label

added releasedpublished label and removed releasedcandidate label

mentioned in merge request !72448 (merged)

added typemaintenance label