fixup! [Docs] Add DR002 for versioning in codegen

Clarify that even if its possible to generate only a subset of per-trait
versions, doing so would mean maintenance burden of a long configuration

Signed-off-by: David Feltell <[email protected]>

Author: feltech

decisions/DR002-Versioning-traits-and-specifications-codegen.md

@@ -206,7 +206,9 @@ from openassetio_mediacreation.specifications.twoDimensional import ImageSpecifi
   history) is a potential source of accidental breakages to backward
   compatibility.
 - Generating all possible versions bloats an application's distribution,
-  when it may only use a small subset of them.
+  when it may only use a small subset of them. Configuring which
+  versions to generate would mean maintaining a long list of options,
+  one per trait.
 - Higher level branching on a schema version is never possible.
 - A specification's version must be bumped when a constituent trait has
   a version bump, even if nothing else in the specification has changed.