Fix usages / Suggestion support for selective preferred / ignored

### Description

In the application resource, there are same named classes, that I never want to directly use, but every suggestions or the function „fix usages“ works with them and still ask me if I mean them...

Some of them I can selectively add into the ignore, but some of them I can't, because i need their interface (methods, properties) suggestions, but the code works just with extended same named (in different namespace) class.

For example, the framework comes with:

```php
less errors in the code

### Related issues

_No response_

### Are you willing to submit a pull request?

I want to, but I'm not a Java developer

### Code of Conduct

Yes

Start by tracing the PHP code-suggestion and Fix Usages flows described in the issue, then identify where preferred and ignored classes are currently handled. The work is complete when a project can selectively prefer the application class while retaining suggestions from the framework class, and both workflows stop repeatedly offering the unwanted same-named class.

Written by the indexing model from the issue text.