Feature Request: Extend file External Tools to allow handling all/many content types in one External Tool manifest

Overview of the Feature Request

As a External Tools administrator, I would like to declare a External Tool scoped to a file where it can be of any content type or of a content type of a list, so that I can declare one single External Tool manifest for all the content types I want to support instead of creating one manifest per content type

What kind of user is the feature intended for?
(Example users roles: API User, Curator, Depositor, Guest, Superuser, Sysadmin)

Guest

What inspired the request?

The Dataverse for OnDemand project that wants to extend Dataverse to download files in Open OnDemand is going to rely on External Tools to trigger the download in OOD. The idea is to use file-scoped External Tools. Creating one External Tool manifest for each downloadeable content type is cumbersome and difficult to maintain. If we had a way to define multiple content types in one External Tool manifest it will be easier to declare.

What existing behavior do you want changed?

Currently we need to create an External Tool manifest for each content type.

Any brand new behavior do you want to add to Dataverse?

We want to define many or all content types in one single External Tool manifest.

Any open or closed issues related to this feature request?

Not yet

Are you thinking about creating a pull request for this feature?
Help is always welcome, is this feature something you or your organization plan to implement?

It would be great to have this feature implemented by a team.

Start by locating the file-scoped External Tools manifest handling and the content-type validation or matching entry points. Define how one manifest should represent many or all content types, then add coverage for the new behavior and confirm existing single-content-type manifests still work.