Override refactor + override in charts + override in Watch

[avouspierre]

The PR includes a large refactoring of the swift part of override/profile functions :

• Override is stored in override core data, including history
• Override preset is stored in overridepreset core data
• Add the display of the override in main graph
• allows to select a override preset (or a temp target) in AW
• allows to cancel a current override preset or specific override (idem for temp target) in AW
• add a color profil for override profil in AW
• Fix some minor code in AW
• add the upload of override as a exercice in Nightscout - Fix #145
• improve the management of indefinate override / stop of indefinate override
• modify the code to respect the Ivan’s patterns of the app :

• Use of swiftInject (dependency injection) with the use of protocol class in the code
• Use of MVP principes, in particular not use of direct coredata in view class
• Use of a proxy model class between coredata and the app to manage changes of core data
• Use of the pattern of observe to refresh data/view/uploads

• add a core data unit tests allowing to add tests for coredata with a in-memory datastore for tests.
• test for overrideStorage available

This PR do NOT change the logic with oref and the interface of override informations in oref. This PR do NOT require a update of trio-oref code.

TODO : Changes the shortcuts after merging with PR #144 and add watch for overrides.

The PR replaces the PR #178 with the functionality for Apple Watch.

override display	override in NS

[mountrcg]

@avouspierre could there be a function that for at least a timewise unrestricted override to copy the new basal profile to the pump? Of course that needs another copy to pump call when override is cancelled!

[dnzxy]

This PR seems to be under active development and has elements that collide with #235 and #236 respectively. May I make two proposals:

1. Let’s put this in Draft mode for now until both the linked PRs are done and we know how the UX will be like before you refactor this.
2. Split this PR so that all elements that regard the watch app for Trio are in a second PR. This PR is really big and hard to review now.

[avouspierre]

This PR seems to be under active development and has elements that collide with #235 and #236 respectively. May I make two proposals:

1. Let’s put this in Draft mode for now until both the linked PRs are done and we know how the UX will be like before you refactor this.
2. Split this PR so that all elements that regard the watch app for Trio are in a second PR. This PR is really big and hard to review now.

OK. I create new PR with different splits.