Allow File Rules to leverage file format metadata

Currently the OCIO File Rules are only based on the path string for the media. This was done intentionally since dealing with file format metadata was deemed too complex for the first pass at the feature. However, it's definitely the case that there often is metadata in the file header that could be useful for determining what the appropriate color space is and it would be useful for the File Rules to be able to leverage it.

We do not want to add any dependencies for file format libraries on to OCIO to support this feature, so it needs to be implemented in such a way that the host application parses the files and provides the metadata in some neutral representation, such as a pair of field & value strings. OpenImageIO has some techniques for representing file-format agnostic metadata that might be a good model for how this could work (without adding a dependency on OIIO).

Of course the metadata in file headers is often wrong, so there needs to be sufficient control in the File Rules to control the relative precedence of what is in the file relative to the existing path-based rules.

Here is a presentation that [discussed OpenEXR](https://docs.google.com/presentation/d/1sY55UHYi2AJF6EPYDYY-mvaJUCzZCkWisrj-a9yhg2w/edit?usp=sharing) that is related.

Commencez par examiner les OCIO File Rules existantes et la présentation OpenEXR liée. Définissez comment sont représentées les métadonnées de champs et de valeurs fournies par l’hôte, ainsi que la manière dont leur précédence par rapport aux règles basées sur le chemin est contrôlée. Le travail est considéré comme terminé lorsque File Rules peut utiliser des métadonnées neutres sans ajouter de dépendances à des bibliothèques de formats de fichiers.

Rédigé par le modèle d'indexation à partir du texte de l'issue.