Various bug fixes for reading from MidasCivil

[peterjamesnugent]

Issues addressed by this PR

Closes #225
Closes #227
Closes #228
Closes #229

Test files

https://burohappold.sharepoint.com/:f:/s/BHoM/EtPgDV8xjf5Dtu5THK-BpJ8BxZe7XfRLQ1nXUlGHHlY_Wg?e=BBh5sm

Changelog

• Added string.Trim() to strings being read from MCT files to ensure section names are correct
• Fixed bug where reading ISection from MidasCivil used a deprecated method and produced inconceivable sections
• Fixed bug where BarPointLoad, BarUniformlyDistributedLoadandBarVaryingDistributedLoadreferenced the wrong index forName` properties
• Fixed bug where GravityLoad referenced the wrong indexes
• Removed official support for MidasCivil, the majority of functionality should still work but we are unable to test MidasCivil 2018 in particular GravityLoad which was causing issues for Midas Civil 2019 onwards

Additional comments

Three tests:

1. Push to non existing - the Adapter should recognise Section1, Section2 etc. already exist and not push
2. Read a model, and then combine the files and load it in to MidasCivil. This will confirm that the trimming of properties has not affected any functionality.
3. Added a third script to test pushing elements, loads and pulling loads

[peterjamesnugent]

/azp run MidasCivil_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[peterjamesnugent]

/azp run MidasCivil_Toolkit.CheckInstaller

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[StephennipBH]

I have pushed the file according to the steps but Midas is not able to read the .mct files.

[peterjamesnugent]

/azp run MidasCivil_Toolkit.CheckCompliance

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[peterjamesnugent]

/azp run MidasCivil_Toolkit.CheckInstaller

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[StephennipBH]

The changes work as intended. Changes approved.