Please, exclude /resources so we can use third-party dashboard 2.0 widgets

[regystro]

Hi and thanks for your time. Regarding this comment:

If the path is purely /resources/ we could look to exclude it.

Originally posted by @sinclairpaul in #2079

Now that Node-RED Dashboard (v1) is no longer bundled and Flowfuse's Dashboard 2.0 is what we're using, I'd like to revisit this issue that triggers Home Assistant's user authentication.

As shown in the official documentation, "If the widget is a third-party widget, we load the relevant .umd.js file, exposed by the widget's /resources folder". So that would be a fixed path.

Steps to reproduce:

1. Install any third party Dashboard 2.0 widgets from here. I'm using ui-frame to keep things simple.
2. Add the widget to any flow of your Node-RED panel, assign it to a dashboard 2.0 page and deploy
3. Try the /endpoint/ URL (in my case http://homeassistant.local:1880/endpoint/dashboard/demos)
4. You need to enter Home Assistant username and password in order to make it work, because ui-frame is trying to load http://homeassistant.local:1880/resources/@flowfuse/node-red-dashboard-2-ui-iframe/ui-iframe.umd.js

Instead of leaving front door open, would it be possible to add an exception to /resources/* to avoid authentication, or map it to the correct location?

Thank you very much in advance.