Migrate Seesaw from .Net IoT to .NET nanoFramework

[usmanatron]

Description

• Migrate Seesaw package from .Net IoT to nanoFramework. Followed the same principles as with the other devices.
• Minimal changes were needed to the actual code, though I tidied up the samples to make them easier to work with.
• Most interesting change is the GpioDriver - I don't think it's needed anymore so I removed it.

Motivation and Context

• Resolves nanoFramework/Home#862

How Has This Been Tested?

I don't have a Seesaw to test against. Everything compiles!

Screenshots

N/A

Types of changes

• [x] Improvement (non-breaking change that improves a feature, code or algorithm)
• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Config and build (change in the configuration and build system, has no impact on code or features)
• [ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
• [ ] Unit Tests (work on Unit Tests, has no impact on code or features)
• [x] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

• [x] My code follows the code style of this project.
• [x] My change requires a change to the documentation.
• [x] I have updated the documentation accordingly.
• [x] I have read the CONTRIBUTING document.
• [ ] I have added tests to cover my changes.
• [ ] All new and existing tests passed.

[usmanatron]

Azure Build is failing due to a NullRef when checking the nuspec. I thought that was because the versions were wrong but it still seems unhappy.

[josesimoes]

@usmanatron nanovc fixed and build running again.

(you'll notice that some dependencies have their IDs wrong in nuspec)

[josesimoes]

@usmanatron can you please fix the merge conflicts that popped?

[josesimoes]

@usmanatron not wanting to push you but doing it... 😁 any chance to get this done so it can be merged?

[josesimoes]

@usmanatron this is getting behind... will you be handling this and bring it up to speed or should we take over?

[networkfusion]

@usmanatron any update?

[Ellerbach]

@usmanatron will you have the time to continue the work? The branch is quite behind the current one and you still have to address some of the comments. Thanks!

[Ellerbach]

@usmanatron any update on this work started in January?

[josesimoes]

hey @usmanatron any plans to resume work on this? 😃

[networkfusion]

Given no update in 2 years, I am going to close this PR as superseeded with #1036.