Add new feature notice for dark mode

[dhruvkb]

Fixes

Fixes #4157 by @fcoveram

Description

This PR

• adds a new VFeatureNotice component that can be used for notifying people of new features
• adds a component VDarkModeFeatureNotice that uses the above to notify people that we now have a dark mode
• adds a spinning-glowing effect to the VSelectField based on the showNewHighlight boolean prop
• adds some logic to hide the notice and glow once the user has interacted with the feature
• does not add logic to remove the notice based on time because we can do that with cleanup in a subsequent deployment

Testing Instructions

0. Check out the PR and run the dev server.
1. Enable the "dark_mode_ui_toggle" feature.
2. Navigate to the homepage. You should see the notice and the glow effect around theme selector.
3. Click on the "See more" button in the notice or the theme selector. The notice and glow will go away, forever (or until you clear cookies).

Checklist

• My pull request has a descriptive title (not a vague title likeUpdate index.md).
• My pull request targets the default branch of the repository (main) or a parent feature branch.
• My commit messages follow best practices.
• My code follows the established code style of the repository.
• I added or updated tests for the changes I made (if applicable).
• I added or updated documentation (if applicable).
• I tried running the project locally and verified that there are no visible errors.
• I ran the DAG documentation generator (ov just catalog/generate-docs for catalog
  PRs) or the media properties generator (ov just catalog/generate-docs media-props
  for the catalog or ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin

Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.


Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

[dhruvkb]

In accordance with #4936, the feature notice border has been changed to a single color instead of a gradient. The homepage color change should be a separate PR as that will involve some snapshot changes.

[github-actions]

Full-stack documentation: https://docs.openverse.org/_preview/4922

Please note that GitHub pages takes a little time to deploy newly pushed code, if the links above don't work or you see old versions, wait 5 minutes and try again.

You can check the GitHub pages deployment action list to see the current status of the deployments.

[obulat]

Sorry you had to spend so much time with the snapshots, but I'm glad that they did find a [small] problem with the language select size. Fixing it is the blocking request for change.

[obulat]

Perfect ✨
Could you add a note in the Dark mode project to replace the link in the feature notice?

[obulat]

In general, I don't like to have a fixed width for an element that has text because it might overflow if a different language has longer text. But I tried Russian, which is usually longer, and it seems to fit. Hopefully, all other languages do, too.

[dhruvkb]

I did this because it was "Fixed" in Figma. When Francisco uses "Fixed" over "Hug", I usually see that as a sign that text is meant to wrap in those scenarios.

[obulat]

Nice addition! It would be useful for the focus ring outlines.