Fix constraint sync during migration
- restore constraints lost during merge in test schema.
- use constraint_by_eid in BeforeDeleteCWConstraintHook as done in
3.17.14 for BeforeDeleteConstrainedByHook. Fixes handling of multiple
constraints of the same type.
- make sync_schema_props_perms() delete the CWConstraint entity instead
of the constrained_by relation. In 3.19, the latter doesn't
automatically result in the former just because the relation is
composite. Simplify the constraint migration to delete all removed
constraints and recreate new ones even if they share the same type; that
optimization made the code more complicated for (AFAICT) no significant
reason.
<table class="attributeForm" style="width:100%;"
tal:attributes="id tab_id | nothing;
class tab_class | nothing;">
<tr tal:iter="widget lines">
<th class="labelCol" tal:content="structure python:widget.render_label(entity)">attrname</th>
<td tal:define="error python:widget.render_error(entity)" style="width:100%;"
tal:attributes="class python:error and 'error' or nothing">
<div tal:replace="structure error">error message if any</div>
<div tal:replace="structure python:widget.edit_render(entity)" >widget (input, textarea, etc.)</div>
<div tal:replace="structure python:widget.render_help(entity)">format help if any</div>
</td>
</tr>
</table>