Restructure project file tree

[luetkemj]

Description

Restructure project file tree to be more explicit in it's naming convention and organization

Related Issue

Motivation and Context

Previously this project followed a file structure that favored simplicity over explicitness. This was difficult during development as it made understanding the name and purpose of a given file more challenging.

some.component/
-- index.js
-- test.js
-- style.js

becomes

components/
-- some/
---- some.component.js
---- some.component.test.js
---- some.component.style.js

Tests are still grouped with the file they are testing which I liked a lot but individual filenames are far more explicit which makes searching for files and recognizing a file by it's filename in a tab far easier.

Screenshots (if appropriate):

Types of changes

• What types of changes does your code introduce? Put an x in all the boxes that apply:
• [ ] 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)
• [x] Style change (non-breaking change that adds no functionality or fixes an issue)

Checklist:

• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.
• [x] I have added tests to cover my changes.
• [x] All new and existing tests passed.
• [ ] I have added a screenshot if appropriate.
• Tested in
• [ ] Chrome
• [ ] Safari
• [ ] Firefox
• [ ] Edge