Convert HTML footnotes to Markdown

What does this MR do and why?

• Converts all HTML footnotes to Markdown
• Moves the content to the table itself when possible
• For unordered lists, uses NOTE where the information belongs instead of footnotes

For the related guidance, see https://docs.gitlab.com/ee/development/documentation/styleguide/#footnote-format.

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.

changed milestone to %16.11

added Technical Writing docs-only docsimprovement documentation maintenancerefactor typemaintenance labels

assigned to @ashrafkhamis

	1 Warning
	45acd04d: Commits that change 30 or more lines across at least 3 files should describe these changes in the commit body. For more information, take a look at our Commit message guidelines.

	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/groups.md (Link to current live version)
• doc/user/application_security/dependency_list/index.md (Link to current live version)
• doc/user/application_security/iac_scanning/index.md (Link to current live version)
• doc/user/application_security/sast/analyzers.md (Link to current live version)
• doc/user/group/import/index.md (Link to current live version)
• doc/user/project/members/index.md (Link to current live version)
• doc/user/gitlab_duo_chat.md (Link to current live version)

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

resolved all threads

added 1 commit

• eb3e4593 - Apply 14 suggestion(s) to 6 file(s)

Compare with previous version