Add `export_fault_lines()` one liner export

[mferrera]

Currently fault polygons are exported from RMS projects in the following way:

• Specify the horizon names
• Specify a folder, under the assumption this folder exists for each horizon
• Loop through each horizon, and if that folder is there and not empty,
  • Create an xtgeo.Polygon from the RMS polygon
  • Create an ExportData instance for each file format being exported
  • Set the polygon fileformat
  • Export

Simplification

A possible one-liner export could instead look something like this:

for category_name in HORIZON_NAMES:
    export_fault_lines(
        project: Any, 
        category_name: str,
        vertical_domain: str = "depth",  # or "time"
        config_path: str | Path = "../../fmuconfig/output/global_variables.yml",
        classification: str | None = None, # Actual default from config
    )

This means we will provide defaults for tagname, name, and workflow (and anything else not listed). This provides a good substrate to accomplish standardization and guide assets to conforming to a single way of doing it, while also allowing an escape hatch of using ExportData directly to deviate from them.

TODO

• How should we structure the aforementioned defaulted values (tagname, name, workflow)?

Tasks

• [ ] Implement the function
• [ ] Update documentation and examples
  • [ ] https://fmu-dataio.readthedocs.io/en/latest/examples.html#exporting-fault-polygons

[mferrera]

Consider naming this fault_lines over fault_polygons to prefer the data product over the data type.

[mferrera]

Sept 25 2024 - updated root comment with refinement from discussions and removing the list of unanswered questions as we have now mostly answered them. This is now approaching "final".