Migrate Convert methods to Adapter, change Engine.Lusas namespace to Adapters.Lusas, add formatting to all documents and implement local versioning

[peterjamesnugent]

Issues addressed by this PR

Closes #236
Closes #239
Closes #247

Test files

https://burohappold.sharepoint.com/:f:/s/BHoM/EjHwiuHBSGpJgmezKPl-UrAB2j6dvBUAkXNDrzl1qDcv9g?e=Zx7Wkw

Additional Comments

@calumlockhart-bh when reviewing there are a few things to check:

• Make sure you're on the latest branches for BHoM, BHoM_Engine, BHoM_Adapter, and BHoM_UI
• Make sure you clone the Versioning_Toolkit too
• When you open the VersioningComponents.gh all the components on the canvas should work, there should not be any error messages and all constructors should produce objects
• Can you also test a push and pull of the simple truss model in PushPullTest.cs, I just want to make sure in the porting of methods and changing of namespaces nothing has fallen through the cracks
• You can check the CreateObject, Compute, Modify and Query components and their respective dropdown lists to see that all the methods fall under the Lusas heading (and not the Adapters heading)
• This will fall under the External heading once it has been fixed in the UI, see BHoM_UI: External subnamespace is explicitly culled out from method tree for components BHoM_UI#223
• Happy for you to just do a few spot checks on the formatting, it's more for our benefit than anything else

Changelog

• Moved methods in .Lusas namespace to .Adapters.Lusas namespace
• Implemented localised versioning for Lusas_Engine stored in Versioning_32.json
• Ported all Convert methods that use the LPI from Lusas_Engine to Lusas_Adapter
• Added formatting (i.e. headers, line breaks etc.) to all document files

[peterjamesnugent]

/azp run Lusas_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[IsakNaslundBh]

@peterjamesnugent Would you mind raising a PR on Versioning_Toolkit, covering the changes to Midas and Lusas. Can then either merge that one as is, or wait for others to join in with the external changes if needed.

[FraserGreenroyd]

Now the versioning can be done locally on this toolkit, @peterjamesnugent , same as we did on XML_Toolkit? 😄

[peterjamesnugent]

/azp run Lusas_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[peterjamesnugent]

/azp run Lusas_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[peterjamesnugent]

/azp run Lusas_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

Versioning works for changing the components to the latest versions. Potential accidental causes of incorrectly identifying modules as older than they are don't appear to lead to infinite looping. Considerations for future updates may include skipping version numbers where applicable. Some cells in JSON files left intentionally blank, may lead to slower processing, shouldn't be a problem at the current stage of development, but worth considering streamlining for the future.

[ghost]

All functions tested with versioning perform adequately.

Versioning works for changing the components to the latest versions.

Potential accidental causes of incorrectly identifying modules as older than they are don't appear to lead to infinite looping of functions. (Deliberate forcing of errors was picked up by components.)

Considerations for future updates may include skipping version numbers where applicable. If no changes are made, or if changes are subsequently changed later, this will help speed up the processes especially with larger files.

Some of the cells in the JSON files are left intentionally blank, this may lead to slower processing than if they weren't included. However, they shouldn't be a problem at the current stage of development. (worth considering streamlining for the future.)

[peterjamesnugent]

@calumlockhart-bh please review again, the namespaces have changed from External to Adapter as per: BHoM/BHoM_Adapter#213

It should be a case of just opening the script with the new build of Lusas_Toolkit and BHoM_UI.

[peterjamesnugent]

/azp run Lusas_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[ghost]

A few instances of inefficient use of namespaces, but nothing to worry about.
Consider where changing "internal" to "private", what it is that you want to be accessible inside the assembly.