Move base plots to Python_Toolkit

[Tom-Kingstone]

NOTE: Depends on BHoM/Python_Toolkit#147

Issues addressed by this PR

Closes #206

Base plots and helper/utility methods have been moved to Python_Toolkit (see the linked PR at the top)
References to python_toolkit have been made where utility and helper methods have been moved, so that the rest of the toolkit and any user scripts do not break, though plots marked private that were moved will have been updated to python_toolkit.plot.<name-of-plot> and no longer marked as private.

e.g.
from ladybugtools_toolkit.plot._heatmap import heatmap
would become
from python_toolkit.plot.heatmap import heatmap

Test files

run the python unit tests to check that nothing is broken.

Changelog

• Moved python base plot types and some utility methods, see changelog for Python_Toolkit for more information.

Additional comments

[bhombot-ci]

@Tom-Kingstone just to let you know, I have provided a check-installer 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 @Tom-Kingstone on Python_Toolkit

[bhombot-ci]

@Tom-Kingstone just to let you know, I have provided a check-installer 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 @Tom-Kingstone on Python_Toolkit

[bhombot-ci]

@Tom-Kingstone just to let you know, I have provided a check-installer 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 @Tom-Kingstone on Python_Toolkit

[Tom-Kingstone]

@BHoMBot check core
@BHoMBot check compliance
@BHoMBot check versioning

[bhombot-ci]

@Tom-Kingstone to confirm, the following actions are now queued:

• check core
• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance
• check versioning

There are 20 requests in the queue ahead of you.

[Tom-Kingstone]

@BHoMBot check null-handling
@BHoMBot check serialisation
@BHoMBot check unit-tests

[bhombot-ci]

@Tom-Kingstone to confirm, the following actions are now queued:

• check null-handling
• check serialisation
• check unit-tests

There are 37 requests in the queue ahead of you.

[Tom-Kingstone]

@BHoMBot check installer

[bhombot-ci]

@Tom-Kingstone to confirm, the following actions are now queued:

• check installer

[jamesramsden-bh]

Tested with unit tests plus some self spot checks. No critical issues preventing merge. Any non-critical issues should have issues raised separately.

[jamesramsden-bh]

@BHoMBot check required

[bhombot-ci]

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

• check code-compliance
• check documentation-compliance
• check project-compliance
• check core
• check null-handling
• check serialisation
• check versioning
• check installer

[bhombot-ci]

The check installer has already been run previously and recorded as a successful check. This check has not been run again at this time.

[bhombot-ci]

@Tom-Kingstone just to let you know, I have provided a check-ready-to-merge 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 @jamesramsden-bh on Python_Toolkit

[jamesramsden-bh]

@BHoMBot check compliance

[bhombot-ci]

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

• check code-compliance
• check documentation-compliance
• check project-compliance
• check branch-compliance
• check dataset-compliance
• check copyright-compliance

[jamesramsden-bh]

@BHoMBot check unit-tests

[bhombot-ci]

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

• check unit-tests

There are 7 requests in the queue ahead of you.