Dot notation / Support all Mavo functions as methods

[LeaVerou]

Early on in Mavo, we made the decision not to have methods, as we worried that dot notation may be too difficult for novices, whereas functions were already proven to be understood via spreadsheets.
However, nested functions come with a lot of usability issues. The higher the nesting, the more novices struggle to balance parentheses or grok the expression tree.

An interesting design decision in Coda is that they support both, so users can use whichever syntax they’re comfortable with. They call it "dot operator": https://coda.io/resources/courses/formulas-101/tip-dot-operator

I quite like this, and I think it would be fairly easy to implement once vastly is integrated. The methods don't need to actually be available on the objects, we'd just rewrite methods to function calls if the name matches one of the functions in Mavo.Functions. @adamjanicki2 please keep track of this use case. Can we decompose any of it into more general primitives that would make sense to implement in vastly?

[adamjanicki2]

Will keep an eye out for this and start thinking about what could have a place in vastly