bug: fix xml tag order

[DSCaskey]

This PR fixes the order of the groups and images XML tags. Instead of writing those tags as one of those resources is added, the app will now create the tags when the draftblock basepoint is created - maintaining the proper draftblock structure.

<draftBlock name="Draft block 1">
    <calculation>
        <point id="1" mx="0.0520833" my="0.104167" name="A" showPointName="true" type="single" x="0.3125" y="0.416667"/>
    </calculation>
    <modeling/>
    <pieces/>
    <groups/>
    <images/>
</draftBlock>

This closes issue #1213

[what-the-diff[bot]]

PR Summary 📝

Awesome work everyone! Our code is going to read like a well-written novel thanks to these changes! 📚

• Refined Header Comments 🖋️ You'll find our header comments are now crystal clear and organized. A breath of fresh air for anyone new to the code! 🎊

• Integrated DOM Handling Feature 🛠️ Cherish the power of QDomElement as it's now part of our family! This enables us to handle DOM much easier! 😎

• An All-New Commenting Style 👌 We've opted for single-line comments over multi-line block comments for constructors and methods. This makes our code easier on the eyes! 💫

• Renamed Variables and Elements for Clarity 💡 We've worked hard to ensure everything is named logically and sensibly. One key change being patternPiece is now known as draftblock in the AddToFile method, enhancing our code clarity! 👏

• Enhanced XML structure 🚀 Not just renaming, our XML structure in the AddToFile method has also upped its game! New elements, TagGroups and TagDraftImages, have been introduced to the draftblock for better organization. This change will help us navigate the code like professional explorers! 🧭

• Cranked Up Consistency Across Method Documentation 📃 We've vowed for consistency! And, made a big step towards it by unifying our vocabulary in the method documentation. It's now an absolute joy to read! ✨

Great job everyone! Keep those fantastic updates coming! 💪😊