Allow catalogs to work with descriptors without resolvers

[parksb]

What's the problem this PR addresses?

Resolves #6928

How did you fix it?

I modified the catalog plugin to skip binding a descriptor when the descriptor referenced by the catalog protocol is not supported by any resolver.

Since an error occurs when binding a descriptor that has no supporting resolver, I added a check before calling resolver.bindDescriptor. Even if the catalog plugin doesn't resolve the descriptor, an error will still be properly raised during the final resolution step if no resolver can handle the descriptor.

Checklist

• I have read the Contributing Guide.

• I have set the packages that need to be released for my changes to be effective.

• I will check that all automated PR checks pass before the PR gets reviewed.

[arcanis]

Thanks! Can you migrate the test to our integration tests?
https://github.com/parksb/berry/blob/d982143e9704351eb0913b7fe11ff356e092a86b/packages/acceptance-tests/pkg-tests-specs/sources/features/catalogs.test.ts

This will make it more resilient to refactorings (I'm reworking part of the architecture and unit tests won't be reusable without efforts, but integration tests are very easy to port).

[parksb]

Thank you for reviewing the PR :) In the unit tests, I tested the case where 'a descriptor is not supported by any resolver'. However, it wasn't easy to test only this specific case in the integration tests.

I added a plugin that supports a custom protocol via reduceDependency to the integration tests, which tests the case where a custom protocol without a resolver is handled correctly. (720b7cd)

[arcanis]

Thanks!