src.ctf.fs: report support for MIP 1

src.ctf.fs: report support for MIP 1

Implement the "get supported MIP versions" method for the `src.ctf.fs`
component class, with the following logic:

 - Attempt to parse the metadata from the given input
 - If the metadata is CTF 1, the supported range is [0, 1]
 - If the metadata is CTF 2, the supported range is [1, 1]

MIP 1 is necessary to properly represent all the concepts found in CTF
2.  It would be possible to implement a mode "CTF 2 with MIP 0" mode,
perhaps by restricting what can be found in the trace to concepts that can
be represented in MIP 0, but the decision was that it's not worth the
investment right now.

Modify `tests/plugins/src.ctf.fs/succeed/test-succeed.sh` to add a MIP
version axis.

Modify `tests/plugins/sink.text.details/succeed/test-succeed.sh` to add
CTF and MIP version axes.

Modify `tests/plugins/flt.lttng-utils.debug-info/test-succeed.sh` to
restrict the MIP version to 0.  We'll remove that flag and add CTF/MIP
version axes once the debug info component class supports MIP 1.

Modify `tests/plugins/src.ctf.lttng-live/test-live.sh` to restrict the
MIP version to 0 in `test_compare_to_ctf_fs()`, which compares the
output of `src.ctf.lttng-live` to that of `src.ctf.fs`.

Change-Id: Icf8522281dd37c96011bed365b273960dc89a3f3
Signed-off-by: Simon Marchi <simon.marchi@efficios.com>
Reviewed-on: https://review.lttng.org/c/babeltrace/+/12777
Tested-by: jenkins <jenkins@lttng.org>
Reviewed-by: Philippe Proulx <eeppeliteloop@gmail.com>