Add documentation explaining how analyzers obtain dependency information

What does this MR do?

This MR makes the following changes to the Dependency Scanning docs:

• Inserts a Language Versions column in the Supported languages and package managers table.
• Removes the the Package Manager Versions column in the Supported languages and package managers table.
• Adds two new tables:
  • Obtaining dependency information by parsing lockfiles
  • Obtaining dependency information by running a package manager to generate a parsable file

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.

Related to #338176 (closed)