Instead of building the LSP-specific symbols directly while parsing source code, we should extract symbols from a more comprehensive internal model of Spring components that we build while parsing source code.

The internal model of Spring components can then also be provided via an additional API (LSP extension) to feed more information to the UI, for example to allow more sophisticated gutter icons, navigation, etc.

Related issues:

• Add support for potential spring bean references microsoft/vscode-spring-boot-dashboard#290
• Add support for spring potential injection points discovery while indexing #994

This could also allow the validation mechanisms to retrieve Spring component information.