misc: Cleanup and Prep for Arduino IDE

[sleepdefic1t]

Proposed changes

This PR is cleanup prep for upcoming Arduino IDE branch.
It removes unnecessary files and moves others to a cleaner more Arduino-friendly layout.
It also properly configures ./library.json to export packages correctly for external library managers.

The following has been changed:

• removed ./appveyor.yml.
• updated ./library.json package export settings.
• removed ./test/travis.yml.
• moved ./docs/ to ./extras in Arduino builds.
• removed submodule from cmake_example.
• removed ./CMakeSettings.json.
• removed uECC_README.md.
• update keywords.txt.
• moved ./src/bcl to ./src/lib/
• moved ./src/rfc6979 to ./src/lib/
• moved ./src/stl to ./src/lib/
• updated ARDUINO_IDE.sh script to reflect lib/ changes.
• updated PIO include and filter paths.

All tests pass locally:

• macOS - CMake.
• macOS - PlatformIO.
• macOS - Arduino IDE

Types of changes

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Refactoring (improve a current implementation without adding a new feature or fixing a bug)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Build (changes that affect the build system)
• Docs (documentation only changes)
• Test (adding missing tests or fixing existing tests)
• Other... Please describe:

Checklist

• I have read the CONTRIBUTING documentation
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[ghost]

@air1one @faustbrian - please review this in the next few days. Be sure to explicitly select labels so I know what's going on.

If no reviewer appears after a week, a reminder will be sent out.

[ghost]

@sleepdefic1t Your pull request needs some changes. Please wait for a comment from one of our developers for more information.

[ciband]

Also, why are we moving the docs into extras? I thought the normal pattern was to have docs at the top level directory.

[ghost]

@sleepdefic1t The ci/circleci: build-linux-default job is failing as of bf803204cb9e941b93bcd3622edd10cc40bf8a4e. Please review the logs for more information.

Once you've pushed the fixes, the build will automatically re-run. Thanks!

[sleepdefic1t]

@ciband docs now only moved on Arduino builds 👍

[sleepdefic1t]

This should be good to go now 👍

[ciband]

@sleepdefic1t

This PR broke Visual Studio support on Windows (CMakeSettings.json) as well as Windows CI support via Appveyor (.appveyor.yml).

Do we still want to support Windows?

[sleepdefic1t]

@ciband
Yes.
Windows dev is an entirely different beast, but we’d still like to support it.

Is this something you’d be interested in tackling?

[ciband]

I can. We technically still have it as you can do cmake from the command line. That process is exactly the same across all platforms. We broke the nice visual studio integration by deleting the CMakeSettings.json.

For Windows CI, I've been trying to get Ark to setup the Appveyor repo since the beginning of time. The .appveyor.yml file should be all that is needed once that account is setup. Someone from Ark will need to create the account and binding the GItHub repo to it (similar to Circle-CI). There was a long standing PR open on this that I think the stale bot closed.

[sleepdefic1t]

@ciband
Appveyor should already be enabled for the C++ SDK’s; so yes, the configs would just need put in place 👍