Support conversion between vector<Any> and vector<typename T::value_type>

[dyackzan]

These changes make way for us to do general vector operations like iterate over, index, append, and remove using BT.CPP. Using vector<Any> objects on the blackboard allows us to create these operations as singletons, rather than requiring each operation to be templated for each vector<T>

The 2 primary components to this PR:

• In setOutput, convert vector<T> objects to vector<Any> before placing them on the blackboard
• In getInput, attempt to unwrap and convert vector<Any> to vector<T> if a vector<T> is expected

[nbbrooks]

Could you document the gcc and clang demangled output for the std::vector<std::string> for reference here in the PR if it isn't possible to add a unit test establishing the demangled output passes the regex max? Ideally we'd have a unit test for partial specialization as well.

[dyackzan]

I checked clang and gcc with the type demangler and get the the same output for the demangled typeid of a std::vector<string> for both:

std::vector<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >, std::allocator<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > > >

[nbbrooks]

Oops, when I hit approve I lost track of my tabs and thought I was approving a submodule update to point to this PR branch 🤦

[facontidavide]

looks like a good addition. Can you please:

• use pre-commit to fix the formatting?
• add a simple unit test too?

[dyackzan]

How does that look @facontidavide ?

[dyackzan]

Tagging @facontidavide , could you give me another review on this?

[dyackzan]

Friendly ping @facontidavide , please let me know if there's anything else you'd like me to change here. We want to keep our fork as up to date with your base as possible