Removed uses of gcc internal, std::_Tuple_impl and updated Base::Join.

Lots of clean-up.

#### Util::ForEach(Tuple, UnaryFn)
__Don't need index, pass a lambda.__
```
std::tuple<int, std::string> tuple(0, "begin");
std::istringstream strm("1 end");
ForEach(tuple, [](const auto &elem) { std::cout << elem << std::endl; });
ForEach(tuple, [&strm](auto &elem) { strm >> elem; });
ForEach(tuple, [](const auto &elem) { std::cout << elem << std::endl; });
```
Prints:
```
0
begin
1
end
```
__Need the index, pass a functor.__
```
struct TPrint {
  
  explicit TPrint(std::ostream &strm) : Strm(strm) {}

  template <std::size_t I, typename TElem>
  void operator()(const TElem &elem) const {
    (I ? Strm << ", " : Strm) << elem;
  }

  private:

  std::ostream &Strm;

};  // TPrint

ForEach(tuple, TPrint(std::cout));
```
Prints: `1, end`

#### Base::Join(Container, Delimiter, Format?)
```
auto tuple = std::make_tuple(42, 1.1, "hello");
std::cout << Base::Join(tuple,
                        ", ",
                        [](std::ostream &strm, const auto &elem) {
                          strm << '(' << elem << ')';
                        }) << std::endl;
```
Prints: `(42), (1.1), (hello)`

If `Format` function is not provided, it defaults to: `[](auto &strm, const auto &elem) { strm << elem; }`

#### Base::AsStr(Arg)
Back to being a one argument function. If you're looking for the variadic version, use the `std::tuple` specialization for `Join`.

Example:
```
std::string text = AsStr(Join(std::forward_as_tuple(42, 1.1, "hello"),
                              ' ',
                              [](std::ostream &strm, const auto &elem) {
                                strm << '[' << elem << ']';
                              });
std::cout << text << std::endl;
```
Prints: `[42] [1.1] [hello]`
Yeah, I considered that. However, my thought was that concatting with neither a delimiter nor a formatter for elements is not a common pattern. I'll provide a `AsStrTuple` if we can find at least 2 places in our codebase where we want that behavior.