Drop kListBegin/End alltogether

Author: andy31415

src/app/interaction-model/Model.h

@@ -77,11 +77,6 @@ class Model : public DataModelMetadataTree
     /// When this is invoked, caller is expected to have already done some validations:
     ///    - cluster `data version` has been checked for the incoming request if applicable
     ///
-    /// List operation support:
-    ///    - the first list write will have `request.writeFlags.Has(WriteFlags::kListBegin)`
-    ///    - the last list write will have `request.writeFlags.Has(WriteFlags::kListEnd)`
-    ///    - the last list write MAY have empty data (no list items)
-    ///
     /// When `request.writeFlags.Has(WriteFlags::kForceInternal)` the request is from an internal app update
     /// and SHOULD bypass some internal checks (like timed enforcement, potentially read-only restrictions)
     ///

src/app/interaction-model/OperationTypes.h

@@ -67,8 +67,6 @@ struct ReadState
 enum class WriteFlags : uint32_t
 {
     kTimed     = 0x0001, // Received as a 2nd command after a timed invoke
-    kListBegin = 0x0002, // Flag is for the first write in a list attribute
-    kListEnd   = 0x0004, // Flag is set for the last write in a list attribute (and that write may be empty)
 };
 
 struct WriteAttributeRequest : OperationRequest