### TL;DR
This pull request refactors the directory structure of the `AuthHeader` component, moving it to the `Pages/Auth` directory. The meta property's attributes were also refined.
### What changed?
The `AuthHeader` component and its story were relocated from the `packages/frontend/src/stories/` directory to the `packages/frontend/src/stories/Pages/Auth/` directory. The title in the meta property has been updated to `Pages/Auth/Header`. The previously explicit assertion that meta satisfies `Meta<typeof Header>` has been removed, making the type assertion implicit.
### How to test?
To test these changes, navigate to the new directory and any references associated with `AuthHeader` component, verify that the software builds successfully, and confirm that Storybook correctly displays the AuthHeader story.
### Why make this change?
This change improves the organization of the codebase by categorizing components into functionally relevant directories. This allows for better management and scalability of the code. Additionally, the adjustments made to the component's metadata in Storybook makes the documentation easier to understand.
### TL;DR
This PR updates formatting in `Button.stories.tsx`
### What changed?
Pulled the Button heading inside `<h1>` tags onto a new line for readability and consistency.
### How to test?
Check the Button story in Storybook and ensure that the Button title displays correctly.
### Why make this change?
This small change improves the readability and consistency of code in the `Button` story.
### TL;DR
Updated paths in `tsconfig.json` and `vite.config.ts`
### What changed?
The paths for `pages` and `types` have been added to both `tsconfig.json` and `vite.config.ts` to support easier importing.
### How to test?
Check if imports using the new paths are working correctly in the code.
### Why make this change?
These changes seem to be for better organization and accessibility of different parts of the code by providing clear and quick paths for `pages` and `types`.
### TL;DR
Added a toast notification for 'Sign-in with Passkeys' feature which is still under development.
### What changed?
'The Sign-in with Passkey' button now triggers a toast notification informing the user that this feature is coming soon.
### How to test?
Click on the 'Sign-in with Passkey' button on the login page. You should see a notification with the message 'Sign-in with Passkeys is coming soon!'.
### Why make this change?
This change has been made to inform users about upcoming features in an interactive manner and ensure a smooth user experience by preventing confusion about non-functional buttons.
