Docs: Update Acronyms.yml to include more acronyms

What does this MR do?

Update acronyms list in Acronyms.yml to include more well-known acronyms

As of commit 6957c52c (latest)

Before:

✖ 0 errors, 772 warnings and 0 suggestions in 1265 files

After:

✖ 0 errors, 752 warnings and 0 suggestions in 1265 files.

For new acronyms and the expanded acronym, see this comment

As of commit d8c02b72

Before:

✖ 0 errors, 786 warnings and 0 suggestions in 1263 files

After:

✖ 0 errors, 712 warnings and 0 suggestions in 1263 files

Acronym	Expanded acronym
ACID	Atomicity, Consistency, Isolation, Durability
ACL	Access Control List
ADFS	Active Directory Federation Services
AMI	Amazon Machine Image
CDN	Content Delivery Network
FIFO	First In, First Out
FTP	File Transfer Protocol
GPU	Graphics Processing Unit
HSL	Hue, Saturation, Luminance
HSTS	HTTP Strict Transport Security
NDA	Non-Disclosure Agreement
OOO	Out of Office
ORM	Object-Relational Mapping
OSI	Open Source Initiative
OSS	Open Source Software
OTP	One-Time Password
POSIX	Portable Operating System Interface
RAID	Redundant Array of Independent Disks
RDBMS	Relational Database Management System
SFTP	SSH File Transfer Protocol
SNI	Server Name Indication
VPN	Virtual Private Network
ZFS	Zettabyte File System

Related issues

Relates to #276199 (closed)

Author's checklist (required)

• Follow the Documentation Guidelines and Style Guide.
• If you have Developer permissions or higher:
  • Ensure that the product tier badge is added to doc's h1.
  • Apply the documentation label, plus:
    • The corresponding DevOps stage and group labels, if applicable.
    • development guidelines when changing docs under doc/development/*, CONTRIBUTING.md, or README.md.
    • development guidelines and Documentation guidelines when changing docs under development/documentation/*.
    • development guidelines and Description templates (.gitlab/*) when creating/updating issue and MR description templates.
  • Request a review from the designated Technical Writer.

Do not add the feature, frontend, backend, ~"bug", or database labels if you are only updating documentation. These labels will cause the MR to be added to code verification QA issues.

Review checklist

All reviewers can help ensure accuracy, clarity, completeness, and adherence to the Documentation Guidelines and Style Guide.

1. Primary Reviewer

• Review by a code reviewer or other selected colleague to confirm accuracy, clarity, and completeness. This can be skipped for minor fixes without substantive content changes.

2. Technical Writer

• Technical writer review. If not requested for this MR, must be scheduled post-merge. To request for this MR, assign the writer listed for the applicable DevOps stage.
  • Ensure docs metadata are present and up-to-date.
  • Ensure Technical Writing and documentation are added.
  • Add the corresponding docs:: scoped label.
  • If working on UI text, add the corresponding UI Text scoped label.
  • Add twdoing when starting work on the MR.
  • Add twfinished if Technical Writing team work on the MR is complete but it remains open.

For more information about labels, see Technical Writing workflows - Labels.

For suggestions that you are confident don't need to be reviewed, change them locally and push a commit directly to save others from unneeded reviews. For example:

• Clear typos, like this is a typpo.
• Minor issues, like single quotes instead of double quotes, Oxford commas, and periods.

For more information, see our documentation on Merging a merge request.

3. Maintainer

1. Review by assigned maintainer, who can always request/require the above reviews. Maintainer's review can occur before or after a technical writer review.
2. Ensure a release milestone is set.
3. If there has not been a technical writer review, create an issue for one using the Doc Review template.

Related issues

Related to #333004