Add the explicit request to add eventList and eventCount into the gen…

…erated struct. (#25316)

Previous change just added them directly in the generation code, which promptly
destroyed all backwards compatibility. With this approach, the default zap
generates as it "always did", but you can request an override to do things
like add new elements, or reorder them.

This should go hand it hand with the PR:
  project-chip/zap#948

If ZAP PR gets merged first, Matter will stay broken with latest zap until this commit is merge in.
Matter, however, can merge this commit first without ill effect, and use older zap if it chooses.

src/app/zap-templates/templates/app/endpoint_config.zapt

@@ -52,7 +52,7 @@
 // This is an array of EmberAfCluster structures.
 #define GENERATED_CLUSTER_COUNT {{endpoint_cluster_count}}
 // clang-format off
-#define GENERATED_CLUSTERS {{chip_endpoint_cluster_list}}
+#define GENERATED_CLUSTERS {{chip_endpoint_cluster_list order="clusterId,attributes,attributeCount,clusterSize,mask,functions,acceptedCommandList,generatedCommandList,eventList,eventCount"}}
 // clang-format on
 
 #define ZAP_FIXED_ENDPOINT_DATA_VERSION_COUNT {{chip_endpoint_data_version_count}}