Work in SPIFFS

[josesimoes]

Description

• Brought SPIFFS config up to date.
• Add support for second SPIFFS instance.
• Rework ORGPAL3 to use 2 SPIFFS instances.
• Improve Windows_Storage_StorageFolder to handle multiple SPIFFS instances.
• Update SPIFFS code to use specific hal calls when multiple instances are present.
• Improvements and fixes with various functions in StorageFolder class.
  • Add initializers to several structs.
  • Add checks for operations before attempting to call them unnecessarily.
  • Change order of check for internal storage to improve code.
• Update spiffs implementation for ST_STM32F769I_DISCOVERY.
• Revert code formatting changes to easily compare with template config file.

Motivation and Context

• Bring SPIFFS up to date.
• Add support for second SPIFFS instance on ORGPAL3.

How Has This Been Tested?

Screenshots

Types of changes

• 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)
• Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

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

[nfbot]

Hi @josesimoes,

I'm nanoFramework bot.
Thank you for your contribution!

A human will be reviewing it shortly. 😉

[josesimoes]

cc @gligorov

[nfbot]

@josesimoes there are issues with the code style on the source files.
A PR was submitted with the code style fixes. Please click josesimoes#1, review the changes if you want and merge it.

Make sure to follow the project code style. Check the details here on how it works and the tools required to help you with that.