opal_info_support: add component to param pretty output

[ghost]

As a small supplement to #1515 I thought it would be nice to:

1. add component names to the parameter output
2. separate parameter sections with a dashed line according to component ( @rhc54 also liked the visual separation this offers.)

The result is something like:

% ompi_info --params btl all --level 3
        [...]
        MCA btl base: ---------------------------------------------------
        MCA btl base: parameter "btl" (current value: "", data source:
                      default, level: 2 user/detail, type: string)
                      Default selection set of components for the btl
                      framework (<none> means use all components that can
                      be found)
       MCA btl vader: ---------------------------------------------------
       MCA btl vader: parameter "btl_vader_single_copy_mechanism"
                      (current value: "cma", data source: default, level:
                      3 user/all, type: int)
                      Single copy mechanism to use (defaults to best
                      available)
                      Valid values: 1:"cma", 3:"none"
         MCA btl tcp: ---------------------------------------------------
         MCA btl tcp: parameter "btl_tcp_if_include" (current value: "",
                      data source: default, level: 1 user/basic, type:
                      string)
                      Comma-delimited list of devices and/or CIDR
                      notation of networks to use for MPI communication
                      (e.g., "eth0,192.168.0.0/16").  Mutually exclusive
                      with btl_tcp_if_exclude.
         MCA btl tcp: parameter "btl_tcp_if_exclude" (current value:
                      "127.0.0.1/8,sppp", data source: default, level: 1
                      user/basic, type: string)
                      Comma-delimited list of devices and/or CIDR
                      notation of networks to NOT use for MPI
                      communication -- all devices not matching these
                      specifications will be used (e.g.,
                      "eth0,192.168.0.0/16").  If set to a non-default
                      value, it is mutually exclusive with
                      btl_tcp_if_include.
          [...]

[rhc54]

👍