Add support for clearing NB cache for certain project and scan it again

### Description

Unfortunately it is very often when NB doesn't see serious changes in code. For example, there is a `Project A` that depends on `Project B`. `Project A` is compiled without any errors and NB shows no error in the project and its packages.

Now, we do serious changes in `Project B` and compile it. NB shows errors in `Project A`, although `Project A` is again compiled without any errors.

Restarting NB doesn't help. The only solution is to clear NB cache. If there is another ways, please tell me, but I didn't find. That's why I suggest to add functionality that will clear NB cache for certain project and make NB scan this project again.

### Use case/motivation

_No response_

### Related issues

_No response_

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

No

The issue names no files, tests, or entry points. Start by reproducing the stale-cache scenario with dependent Project A and Project B, then locate how NetBeans stores project cache data and triggers project scanning; done means a user can clear one project's cache and rescan it without restarting the IDE.

Written by the indexing model from the issue text.