fix: Explicitly depend on fb_sysfs in fb_storage (#26)

## 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](https://github.com/etsy/chef-cookbooks/blob/99b3e3abc9b42096c6450d9f84582d50aa8e2448/cookbooks/fb_storage/resources/format_devices.rb#L141)), `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?

cookbooks/fb_storage/metadata.rb

@@ -9,3 +9,4 @@
 version '0.0.1'
 supports 'centos'
 depends 'fb_helpers'
+depends 'fb_sysfs'