1. What is the nature and description of the request?

When using remote task resolution with PaC and Tekton Hub, Pipeline as code only supports pulling tasks from a single catalog.  We have multiple catalogs on our internal Tekton Hub server, so we would like a way to specify the catalog source in the task declaration of a PaC pipeline run.  This would allow us to resolve tasks from any of the catalogs on the Hub server without having to specify full url's.

3. Why does the customer need this? (List the business requirements here)

We have multiple tekton catalogs owned by separate teams, which are all synchronized into a central tekton hub instance.  We can only use short name task resolution to one of the catalogs on the server; tasks in the other catalog need to be accessed remotely via their full raw url.

4. How would the customer like to achieve this? (List the functional requirements here)

The implementation details are for the pipelines as code team to decide, but maybe something like ['catalogName::taskName'], ['catalogName::taskname/version'] or ['catalogSource::catalogName::taskName'], etc.

5. For each functional requirement listed in question 4, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.
 
Stand up an instance of tekton hub, synchronize multiple catalogs to the tekton hub instance.  The catalogs should have different names on the hub instance.  Verify a pipelines as code run can pull tasks from each of the synchronized catalogs and the default catalog named 'tekton'.