Partial-order concurrency: permit data races

[tautschnig]

Data races are undefined behaviour, and we shouldn't be giving a semantics for these. Instead, omit write-serialisation constraints when at least one write is non-atomic.

This is work in progress as more debugging is to be done and we need to figure out the right way to conditionally add assertions (for a --data-race-check option).

• Each commit message has a non-empty body, explaining why the change was made.
• Methods or procedures I have added are documented, following the guidelines provided in CODING_STANDARD.md.
• The feature or user visible behaviour I have added or modified has been documented in the User Guide in doc/cprover-manual/
• Regression or unit tests are included, or existing tests cover the modified code (in this case I have detailed which ones those are in the commit message).
• My commit message includes data points confirming performance improvements (if claimed).
• My PR is restricted to a single feature or bugfix.
• White-space or formatting changes outside the feature-related changed lines are in commits of their own.