Baked Table::buildRules() rules are too brief.

Nobody has claimed this yet.

You get something like this:

``` php
$rules->add($rules->isUnique(['email']));
```

When really we want something like this:

``` php
$rules->add(
$rules->isUnique(['email']),
'email-is-unique',
[
'errorField' => 'email',
'message' => 'That email address already exists.',
]
);
```

Without those additional properties, the rule will cause a `save()` to fail, but will **not** report the error anywhere (not even in DebugKit). This is not an acceptable "default" level of quality. We should have the choice to reduce the "verbosity" of the messages, not be forced to add it by rote. That's the whole point of having bake templates, after all.

Start at the Bake Table::buildRules() template or entry point that produces the shown PHP. Compare its generated rule with the requested named rule and additional properties. Done means generated rules include the requested error metadata and a save() failure reports the error, including in DebugKit.

Written by the indexing model from the issue text.