Rebase Multi-Storage bmcweb patches to latest

Update the bmcweb patches that supporting multi-storage with
associations. The current patches still uses tree paths and was not
changed to make sure we don't break anything. The association change
is now needed for NVMe Drives.

Update the bmcweb Storage to follow the Swordfish spec:
https://www.snia.org/sites/default/files/technical-work/swordfish/draft/v1.2.2/pdf/Swordfish_v1.2.2_NVMeMappingGuide.pdf

Tested:
Redfish Validator test passed with no issue on the Drive/Storage.

Drive Upstream/Downgrade works fine.

Internal link with all of the actual test results:
- http://go/gbmccl/117769

Google-Bug-Id: 232038811
Google-Bug-Id: 253298753
Google-Bug-Id: 253298295
Change-Id: I57993843250d24424e6c178eec66d67e400a8491
Signed-off-by: Willy Tu <wltu@google.com>
15 files changed
tree: a631efad5fda32800d190462be36f0352f56bc74
  1. conf/
  2. meta-nuvoton-npcm8xx/
  3. recipes-connectivity/
  4. recipes-google/
  5. recipes-kernel/
  6. recipes-phosphor/
  7. LICENSE
  8. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.