fix: Explicitly depend on fb_sysfs in fb_storage

[russtaylor]

Description

Explicitly includes fb_sysfs as part of the fb_storage cookbook.

Context

When I tried spinning up a different VM type that uses NVMe-based storage, I noticed that chef was failing. After further debugging, I realized that in certain cases (such as for NVMe devices), fb_storage calls out to fb_sysfs. However, fb_storage never explicitly includes fb_sysfs, so by default it's not available and causes the chef run to fail.

Testing Plan

I ran manual tests via Packer - to do this, I had to manually change the instance size to one that supports hyperdisks (I used c3-standard-22) and then manually attached a hyperdisk to the instance. When I added the explicit depends fb_sysfs, that solved the issue and fb_storage was able to format and mount the drive as expected.

Other Considerations

I'm not sure what other implications this might have; Maybe there's a reason fb_sysfs wasn't included explicitly and this will cause failures with non-NVMe devices?

[ericnorris]

Same comment as @adsr on Slack - I'm guessing upstream would take this as a PR as well, could we try submitting it there too?