Share struct member definition for parse_options and parse_options_view

[vyasr]

question: It seems a shame that one must repeat most of the fields between parse_options and parse_options_view. Shall we open an issue to discuss whether these should be shared with something like:

struct _parse_options {
   char delimiter;
   ...;
   ...;
}

struct parse_options_view {
    struct _parse_options opts;
    cudf::detail::trie_view trie_true;
    ...;
}

struct parse_options {
   struct _parse_options opts;
   cudf::detail::optional_tree trie_true;
   ...
   
}

WDYT?

Originally posted by @wence- in #15727 (comment)

[etseidl]

how about something like

template <class TrieT>
struct _parse_options {
  char delimiter;
  ...
  TrieT trie_true;
  TrieT trie_false;
  TrieT trie_na;
  bool multi_delimiter;
};

using parse_options_view = _parse_options<cudf::detail::trie_view>;

struct parse_options : public _parse_options<cudf::detail::optional_trie> {
  [[nodiscard]] json_inference_options_view json_view() const { ... }
  ...
};

cc @vuule