Clarify pipelines/latest REST resource and document a 403 error

What does this MR do and why?

Clarify what is the meaning of "latest" as to not cause confusion with the most recent pipeline seen in the UI. Also document what happens if no pipeline exists.

@jamesreed helped me track this behavior on internal support issue #476205.

Relates to issue: #428343

MR acceptance checklist

Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.