I could find the reference in the ansible scripts and I'm unable to find such artifact path in the main repo. It might be a good idea to use the artifact registry as the central point for downloads, since it would contain properly tagged artifacts from the pipeline.
Looking at GitLab's doc the api for getting artifacts from jobs would require a jobId (https://dev.funkwhale.audio/funkwhale/funkwhale/-/pipelines/37658 in this case).
If the flow migrates to download by release, the tag could be used, similar to https://dev.funkwhale.audio/funkwhale/funkwhale/-/archive/1.4.0-rc2/funkwhale-1.4.0-rc2.zip but exploded to its individual components, so the ansible scripts would be able to have a fixed path to search
Another possibility would be investigating the need of prepending 'project' to the path (even though I was unable to reach the artifacts either way, it's the guidance of the Gitlab Docs when downloading by name )
In this case we'd possibly have ansible authenticate accordingly and reach to https://dev.funkwhale.audio/api/v4/projects/17/jobs/artifacts/1.4.0/download?job=build_front