W-17980476: add functionality to exclude md types from connection resolver

[EstebanRomero84]

What does this PR do?

• Adds new optional parameter to connectionResolver class. This parameter is used to exclude specific types from the result.
• Update CSB to pass the list of excluded types to CS. This fixes a bug where components in folders where included in the resulting CB even if they where not included in the list md types to be retrieved.

What issues does this PR fix or reference?

@W-17980476@
forcedotcom/cli#3232

Functionality Before

Calling sf project generate manifest --from-org my-org --name package --excluded-metadata Dashboard --excluded-metadata Report doesn't exclude Dashboard and Report components from the resulting manifest.

Functionality After

Calling sf project generate manifest --from-org my-org --name package --excluded-metadata Dashboard --excluded-metadata Report excludes Dashboard and Report components from the resulting manifest.

[WillieRuemmele]

I don't love that we're adding another parameter to the constructor. Though it should be a non-breaking change, it still makes me hesitate.

can we do the same logic, but inverting it using mdTypes?

if it's not in mdTypes don't search for, or return it?

or in ComponentSetBuilder, before returning the CS, run it through a filter and remove any of the excluded types?