Ignore submodules separately from `git.*` settings

[bryceschober]

I have noticed #5906, but their desired usage is different than ours.
I have noticed #6719, but that's a different bug that wouldn't serve our use-case even if it were fixed, since it's about using the top-level git.* settings.

I feel that we really do need a githubPullRequests.*-specific version of ignoredRepositories and/or ignoreSubmodules.

The use case I have in mind is that we have several third-party repositories included as submodules, and that we do want to let VSCode be able to help us manage them in general, but are not participating in their development, so don't want them cluttering up our PR view.

If there were a githubPullRequests.ignoreSubmodules setting that could be set in our project workspace or settings file, I would use that, and be happy.

[MichaelHadar]

@alexr00 Is this anywhere on the roadmap? It is very annoying to deal with.

[alexr00]

It wasn't, but Copilot did a pretty good job in #7624.

[MichaelHadar]

@alexr00 I'm talking about the ignoredRepositories feature, which is much more useful.
For example, I'm using a few different repositories that I have full code access to, (not as sub-modules) but do not participate on the development of them. I want to completely ignore them in my pr screen.

Also, the new change does not close this issue, only half of it.

Quoting:

I feel that we really do need a githubPullRequests.*-specific version of ignoredRepositories

But you only implemented githubPullRequests.ignoreSubmodules.