docs: Updates documentation and examples to bring it up to date with 0.0.8 (#128)

* Adds doc comments to all record root options.

* Documentation updates and separated options to a folder.

* Used AI to create lots of examples.

The fact that it's written by AI means its probably a lot more verbose than it could be, but it has pretty good coverage of features, and it saved me ALOT of time.

* `cargo fmt`

Author: lukasfri

xmlity-derive/src/de/DeserializationGroup.md

@@ -11,7 +11,7 @@ To configure the deserialization, use the `#[xgroup(...)]` attribute on the root
 
 ## Configuration
 
-### Serialize a part of an element - `#[xgroup(...)]` on the root of a type
+### Deserialize a part of an element - `#[xgroup(...)]` on the root of a type
 
 #### Root Options
 
@@ -33,10 +33,10 @@ attribute_order
 <code>"strict"</code>, <code>"loose"</code>, <code>"none"</code>
 </td>
 <td>
-The accepted order of attributes.
-- <code>"strict"</code> - The attributes must be in the same order as the fields with no fields between them.
-- <code>"loose"</code> - The attributes must be in the same order as the fields, but there can be fields between them.
-- <code>"none"</code> - The attributes can be in any order.
+Set if the order of attributes is important when deserializing.<br/>
+- <code>"strict"</code>: The attributes must come directly after each other, and this group will try to deserialize them in one go.<br/>
+- <code>"loose"</code>: The order of attributes must come relative to each other, but they can be separated by other attributes outside this group.<br/>
+- <code>"none"</code> (default): The order of attributes is not important.
 </td>
 </tr>
 <!--=================================================-->
@@ -48,10 +48,10 @@ children_order
 <code>"strict"</code>, <code>"loose"</code>, <code>"none"</code>
 </td>
 <td>
-The accepted order of children.
-- <code>"strict"</code> - The children must be in the same order as the fields with no fields between them.
-- <code>"loose"</code> - The children must be in the same order as the fields, but there can be fields between them.
-- <code>"none"</code> - The children can be in any order.
+Set if the order of children is important when deserializing.<br/>
+- <code>"strict"</code>: The children must come directly after each other, and this group will try to deserialize them in one go.<br/>
+- <code>"loose"</code>: The order of children must come relative to each other, but they can be separated by other children outside this group.<br/>
+- <code>"none"</code> (default): The order of children is not important.
 </td>
 </tr>
 <!--=================================================-->