[Feature Request]: Have all settings behind /settings URL slug

**Is your feature request related to a problem? Please describe.**
Currently all the admin URLs are `/monitors`, `/proxies`, `/tags` etc. - the (possibly) public URLs are `/status/`. Given firewall rules, it is hard to block all URL slugs, but `/status/*` especially if you are using CNAMEs for the status pages, e.g. `status.example.org` actually represents `/status/`.

**Describe the solution you'd like**
If all setting pages were behind an `/settings` URL slug e.g. `/settings/tags`, `/settings/monitors` etc., one could easily have custom authentication / IP access rules for `/settings/*`. Whether it is `/settings`, `/admin`, `/config` as the base-URL for settings I really don't care.

**Describe alternatives you've considered**
Create manual access rules per URL. The problem is that new setting URLs may be created in the future.

Look at the routing configuration in the codebase to understand how URLs like /monitors and /proxies are currently handled. Identify where route definitions are set up, likely in a main.go or routes file. The change involves adding a /settings prefix to admin routes and ensuring all existing functionality remains accessible. Test by running the application and verifying that /settings/monitors, /settings/proxies, etc., work correctly while public /status/* routes remain unchanged.

Escrito por el modelo de indexación a partir del texto del issue.