Version tagging settings

[vietle-bh]

Issues addressed by this PR

Helps close https://github.com/BuroHappoldEngineering/Revit_Tagging_Tool/issues/179

This pull request introduces several upgrade methods to the v93 upgrader, focusing on improving the migration of tagging settings objects to newer versions. The main enhancements involve flattening nested settings structures and handling property renames or removals to align with updated object models.

New upgrade methods for tagging settings:

• Added UpgradeMEPGlobalTagSettings to flatten the UseExclusionZones property from the nested BhomSettings dictionary to the top level and remove it from the nested dictionary. ([BHoMUpgrades/CustomUpgrades/v93.csR35-R150])
• Added UpgradePointTagSettings to flatten base settings, rename RiserLeaderAngle to OrthogonalLeaderAngle, and remove TagObscuredDisciplineElements. ([BHoMUpgrades/CustomUpgrades/v93.csR35-R150])
• Added UpgradeCurveTagSettings to flatten base settings and remove both KeepTagPlacementPointOnHost and TagObscuredDisciplineElements. ([BHoMUpgrades/CustomUpgrades/v93.csR35-R150])
• Added UpgradeAreaTagSettings to flatten base settings and remove both RiserLeaderAngle and TagObscuredDisciplineElements. ([BHoMUpgrades/CustomUpgrades/v93.csR35-R150])

Helper method for flattening:

• Introduced a private FlattenBaseSettings method to move properties from the nested BaseSettings dictionary to the top level, simplifying the upgrade logic for all tagging settings. ([BHoMUpgrades/CustomUpgrades/v93.csR35-R150])

Test files

Please see https://github.com/BuroHappoldEngineering/Revit_Tagging_Tool/pull/180

Changelog

Additional comments

[bhombot-ci]

@vietle-bh just to let you know, I have provided a check-versioning result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @vietle-bh on Revit_Tagging_Tool

[bhombot-ci]

@vietle-bh just to let you know, I have provided a check-versioning result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @vietle-bh on Revit_Tagging_Tool

[pawelbaran]

Versioning check passing, users are happy, I can only approve 👍

[bhombot-ci]

@vietle-bh just to let you know, I have provided a check-versioning result to this Pull Request as it was detected to be linked to other Pull Requests in a series. The comment which triggered this check came from @vietle-bh on Revit_Tagging_Tool

[vietle-bh]

@BHoMBot check ready-to-merge

[bhombot-ci]

@vietle-bh to confirm, the following actions are now queued:

• check ready-to-merge

There are 300 requests in the queue ahead of you.