264 - Add the AccessFileMenu to File Page

[MellyGray]

What this PR does / why we need it:

This PR adds the AccessFileMenu to the File Page. Since the menu component already existed and was being used in the Files Table from the Dataset Page in its button icon form, I refactored the necessary components to rehuse the component in the File Page.

To refactor the AccessFileMenu component I first needed to extract the File Metadata from the File model. That's why this branch parent is refactor/263-extract-file-metadata

Which issue(s) this PR closes:

• Closes Add the AccessFile button to the File Page #264

Special notes for your reviewer:

Take into account that the button already existed in its icon button shape in the Dataset Page:

Suggestions on how to test this:

1. Install the necessary dependencies using npm install.
2. Build the design system with cd packages/design-system && npm run build.
3. Navigate back to the root directory with cd ../../.
4. Start Storybook with npm run storybook.
5. Visit the File Page in the Storybook and check that the Access File Menu looks as expected
6. For detailed menu stories visit AccessFileMenu stories
7. To ensure that the refactor didn't affect the button in the Files Table, which is the same button but in its button icon shape, take a look at the Access File Menu in the Dataset Page story

Does this PR introduce a user interface change? If mockups are available, please link/include them here:

Is there a release notes update needed for this change?:

No

Additional documentation:

[coveralls]

coverage: 97.595% (-0.3%) from 97.871%
when pulling 7a1ce85 on feature/264-add-the-accessfile-button
into e80a75f on refactor/263-extract-file-metadata.

[M27Mangan]

Looks good to me!

[ekraffmiller]

Looks good! In testing the Embargo option, I found an unrelated bug, added here: #292.