Not having Google Analytics set up results in 404 request

[J4bbi]

Describe the bug
If a repository is not set up to use Google Analytics, the backend responds with a 404 response. If a property hasn't been set (see REST contract for configuration properties).

To Reproduce
Steps to reproduce the behavior:

1. Open up a repository landing page (or any page)
2. Inspect the console

Expected behavior
The frontend should be able to gracefully establish if Google Analytics is disabled.

[tdonohue]

Would require fixing DSpace/DSpace#9014

Or, might be solved by a way to pull down all enabled backend configurations at once (GET /api/config/properties). In that scenario, there would be no need to call this endpoint for individual configs one-by-one, so this 404 response would be rare. But as we know that "findAll" style endpoint doesn't exist yet: https://github.com/DSpace/RestContract/blob/main/configuration.md#main-endpoint

Currently, this endpoint behaves "as designed". I agree though that a 404 response is misleading, as it implies a possible error. But, the intended meaning is simply that the backend configuration "doesn't exist" or isn't enabled/shared.

Overall, sites seeing this can safely ignore the 404. But, I do agree it'd be nice to provide a better response that is not as misleading.