Refactor to improve UX

[FraserGreenroyd]

Following on from the workshop with @EKAdebo last week, the following should be completed to improve UX:

• Remake SAP_Adapter to take in more inputs/arguments/configuration options to pull SAP Reports, and join up information coming in from Excel (currently this is a large amount of components on the Grasshopper canvas, so this will be a simplification exercise).
• Rename the SAP Connection for Argyle from SAP_Adapter to Argyle_Adapter to make things easier for users (specifying the SAP engine effectively via the adapter).

FYI @rboulton-BH @albinber @EKAdebo

[FraserGreenroyd]

Current state of affairs:

SAP Adapter now pulls SAP Reports, marrying up data pulled from Excel, and marrying up to heating templates. This is then used to produce 1 SAP Report per Dwelling on pull.

Push allows for each Dwelling's SAP Report to be pushed to the Argyle SAP XML schema for sending to the Argyle engine.

The XML objects are left within the oM but all have [NoAutoConstructor] attribute to prevent them showing up in the ctrl + shift + b search menu within BHoM - trying to prevent UI clutter for UX (@kprusicka @EKAdebo ).

Need to tidy up the objects and engine files next to complete the refactor. @rboulton-BH is evaluating the workflow compared to existing.

[FraserGreenroyd]

ToDo:

• Params from Config onto Dwelling Schedule - per dwelling
• Parametrics - blend but also look to import from Excel
• Parametrics naming - per @rboulton-BH spreadsheet demoed
• Parametrics - one component per parametric type with one to blend all

[FraserGreenroyd]

All items on the todo have been done - follow up needed with @rboulton-BH