Swap order of selectability/visibility toggles

Just to be consistent with outliner.

Add columns for visibility and selectability toggles

Good example of where the table API is useful: Adding new columns is a
small change.

Use entire width of collections editor for table

Use table background drawing for collections editor

Merge branch 'uiTable' into temp-layers-ui-table

Fix mistakes with background drawing

Draw collection names using layout/button engine

Instead of drawing it directly via BLF call.

Merge branch 'uiTable' into temp-layers-ui-table

Create and pass a uiLayout to cells

Played with a more complex and more efficient version, but that made
things pretty complicated. Now this is a simple, but less optimized, solution.

Support drawing some background color alternating per row

Draw tables row by row, not column by column

Unit tests for uiTable API (and fix bugs found using it :)

Initial commit to use uiTable API for collections editor

Does nothing but drawing a single column for collection name, but it
shows that the API works ;)

Merge branch 'uiTable' into temp-layers-ui-table

Cleanup: Add assert, remove unused variable

Initial implementation of a uiTable API

This adds an initial (and already working), generic API for defining, handling and drawing of table UIs.

It supports two types of tables:
* Vertical flow: Rows are all in a vertical stack.
* Horizontal flow: Rows are stacked vertically, until some threshold height is reached. The table is then split into another vertical stack that is drawn next to the former one. Such drawing could be used for the file browser in non-thumbnail mode.

A table is built out of - guess what - rows and columns. The API allows defining new collumns (identified by an id-name) and inserting new rows at any point. When drawing, we draw a cell for each column/row combination, using a custom cell-drawing callback.
The uiTable API will probably get some support for drawing buttons (uiBut) into custom layouts (uiLayout).

The API is written with big data sets in mind. In future we may get a spreadsheet view where data like all vertices of a mesh is displayed. That would result in thousands of rows, the uiTable API should be ready for this.

Merge remote-tracking branch 'origin/clay-engine' into render-layers

Build Clay engine by default

Another fixup for rB6cdb3845 (Added collection props getter/setter)

Values were getting clamped

Merge remote-tracking branch 'origin/clay-engine' into render-layers