Split curl statements in Documentation

What does this MR do?

Splits existing curl statements within the documentation to fit on page.

Previously, the individual would be required to scroll through the content to see the entire curl statement. Now the curl statement is divided by arguments and line length in an effort to not exceed 120 characters.

This was achieved by executing a Find/Replace of Regex: (curl.{50,})-- with $1\\\n -- to find curl statements exceeding 50 characters with remaining arguments. Then each file was examined by hand to achieve argument alignment and ensure ordering and accuracy.

Closes #332361 (closed)

Screenshots (strongly suggested)

Before (https://docs.gitlab.com/ee/api/users#add-a-gpg-key)	After (http://main-ee-63041.178.62.207.141.nip.io/ee/api/users.html#add-a-gpg-key)

Does this MR meet the acceptance criteria?

Conformity

• [-] I have included a changelog entry, or it's not 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.