Rename flags to enable field access order checking.

The aim of this change is to avoid naming collisions with other flags,
particularly in financial domains where "order" is used frequently.

Author: ZachBray

Safe-Flyweight-Usage.md

@@ -12,16 +12,16 @@ When decoding, failure to follow the contract can result in the misinterpretatio
 
 SBE can generate runtime checks that ensure the correct usage of flyweight encoders/decoders/codecs (w.r.t. field access order) in Java, C++ and C#.
 
-To generate these runtime checks, pass `-Dsbe.generate.access.order.checks=true` when running the SBE tool.
+To generate these runtime checks, pass `-Dsbe.generate.sequencing.checks=true` when running the SBE tool.
 
 By default, the generated checks are disabled, using conditional compilation, as they have a significant performance overhead.
 We expect that teams will enable these runtime checks in non-production environments and in their tests.
 
 To enable the runtime checks:
 
-* In Java, set the `sbe.generate.access.order.checks` system property to `true`.
-* In C++, define the `ENABLE_ACCESS_ORDER_CHECKS` symbol when compiling.
-* In C#, define the `ENABLE_ACCESS_ORDER_CHECKS` symbol when building.
+* In Java, set the `sbe.enable.sequencing.checks` system property to `true`.
+* In C++, define the `SBE_ENABLE_SEQUENCING_CHECKS` symbol when compiling.
+* In C#, define the `SBE_ENABLE_SEQUENCING_CHECKS` symbol when building.
 
 ### Checking complete encoding