Device symlinks created at the wrong path

[arnaldo2792]

What I expected to happen:
I expect that a symlink under /dev is created using the device mapping configured for my EC2 EBS volume.

What actually happened:
In certain workflows, the symlinks to the devices are created under /dev/dev/<device> instead of just /dev/device. Additionally, creating devices under /dev with an actual ID that could be used by the kernel is a bad practice, so we should create the symlinks for EBS volume mappings under /dev/by-ebs-id, to prevent collisions with kernel device names. See amazonlinux/amazon-ec2-utils#37 for reference.

[arnaldo2792]

I forgot to close this in #98