ingoring diagnostics for scopes

I think we have a gap in diagnostic filtering. Consider this scenario:

SGDEX was modified to include pkg:/source/utils.brs and call a single logging function.

SGDEX is ignored from diagnostics like this:

bsconfig.json

{
    "diagnosticFilters": [
         "**/SGDEX/**"
    ]
}

Now consider this diagnostic:

source/utils.brs:10:39 - error BS1001: Cannot find function with name 'UnrelatedFunction' when this file is included in scope 'components/SGDEX/ComponentController/ComponentController.xml'

The diagnostic is attached to pkg:/source/utils.brs, not SGDEX. So there's no way to bulk-ignore all SGDEX-related errors of this type.

To solve this issue, I think we need to make the following changes:

1. modify all diagnostics to include relatedInformation paths to component files (when applicable)
2. modify diagnosticFilters to either
   a. also filter diagnostics based on their relatedInformation paths
   b. modify diagnosticFilters to support a specific relatedInformation filter pattern

The issue does not name specific files, tests, or entry points. Start by locating diagnosticFilters and the diagnostic relatedInformation handling, then determine how component scope paths are represented; done means SGDEX-related diagnostics can be filtered through their associated component paths without losing useful diagnostic information.