Align which unused procedures are reported

Now, implemented interface members and members in class modules marked as interface are reported as unused, if there are no references to them.

In addition, we no longer report unused procedures in in exposed class modules, sine these modules are clearly intended for external use.
We do not treat standard modules without the Private Module option the same way, because not having the option is the default in contrast to the exposed attribute.

Merge pull request #6025 from MDoerner/AlignHandlingOfInterfacesINotUsedInspections

Align handling of interfaces in not used inspections

Handle inconsistent results from Find All references gracefullt

The results of Find All References take the input code from the reference's line in the VBE and the highlight selection based on the reference selection. If this happens in a dirty state, the highlight can be outside the input code on the line that is now on the line the reference was on before. Previously, this caused an ArgumentOutOfBoundExcetion in the UI code when applying the highlight, which brought down the host. Now, we c

Merge pull request #6026 from MDoerner/StopCrashingOnFindReferencesInDirtyState

Handle inconsistent results from Find All references gracefully

> Closes #5907

Issue #5907 points to the existence of a line continuation as the cause of the incorrect `AsTypeName` outcome. However, the issue had nothing to do with the line continuation and everything to do with the '&' operator between the string literals.

The goal of the `ImplicitTypeToExplicitRefactoringAction` is to provide an _improved_ result, when possible, relative to the `DeclareAsExplicitVariantQuickFix`. Absent a unified Expression engine (#3969), the refactoring action is