Build datatable modules with @since, +API updates

Add Loader meta for DataTable

Build datatable-base with column classname fix

Build recordset-base, datatable-base

Build datatable-base, -datasource, and -scroll

Build datatable-base

Build datatable-base and -sort

Build datatable-base and -sort

Remove "Y." from @param and @return for API docs

parentNode check => inDoc(). Fixes #2530730 Stupid IE reports parentNode for detached elements as a nodeType 11 node. That makes pandas sad.

Replace @returns with @return

Regression. Fixes #2530596. So much more I'd like to fix while I'm in there, but it'll have to wait until after 3.4.0.

Avoid attribute API methods in render loops There were a lot of calls to get('attr') within the row and cell rendering loops. The render methods should not be modifying these values during iteration, so it should be safe to capture the values before iteration. Similarly with the determination of cell formatters, all conditional logic and setup can be moved above the row render loop. This should speed up rendering somewhat (see ticket #2530152), though the biggest performance win will be moving away from Node.create to innerHTML string concatenation. That won't happen until 3.5.0. Also while I was in there, I moved UI related event bindings to bindUI and did some other code cleanup.

Restub Y.dump and use Y.Lang.sub in DataTable Fixes #2530546. Prior to commit https://github.com/yui/yui3/commit/0212e3fe3137ecc4fd3d270f14837467f05bfa61#L11R1021 Y.dump was undefined unless the module was included. Y.substitute used a feature test `if (Y.dump)` to fork output formatting of object values through Y.dump if available. With the stub, this test became always true, but the stub was a noop, resulting in Y.dump(...) returning undefined. There are two issues here: 1) Y.dump is expected to return a value 2) DataTable default formatter was using Y.substitute which changed behavior if the dump module was included. It could be that DataTable's use of substitute was purposeful, to support recursive substitution. The replacement of Y.substitute with Y.Lang.sub in the DataTable methods will break this, but there was no use of recursion in any DataTable module, so any breakage would be with custom template overrides. I decided to replace with Y.Lang.sub anyway, because it's possible to work around the loss of recursive substitution, but not so for the behavior change based on the presence of the dump module. There's more discussion about this in commit comments on the linked commit.

Caption is optional. Fixes #2529968 A more comprehensive solution is warranted. At least one that doesn't incur the overhead of creating a caption element even if it's not used. I'm leaving that to the rendering performance pass.

Complete build of every module with the new flattened directory structure