firefox & geoclue: point to api.beacondb.net for beacondb

Functionally identical without need to change, but pointed out for scaling up and routing traffic differently if necessary.

Ref: https://matrix.to/#/matrix.org/$nh0IGqWhdROr-xXAMD9hZxMqyUDgfy6DOabKzh6YPaQ?via=matrix.org&via=tchncs.de&via=nitro.chat

etc/firefox/policies/policies.json

@@ -643,7 +643,7 @@
 				"Status": "locked",
 				"Type": "string",
 				"Value": "",
-				"Value_beacondb": "https://beacondb.net/v1/geolocate",
+				"Value_beacondb": "https://api.beacondb.net/v1/geolocate",
 				"Value_positon": "https://api.positon.xyz/?key=74600654-2aec-11ef-aa95-3b7218da6865"
 			},
 			"geo.provider.use_geoclue": {

etc/geoclue/conf.d/beacondb.conf

@@ -1,10 +1,10 @@
 # https://beacondb.net & https://beacondb.net/map
 [wifi]
 enable=true
-url=https://beacondb.net/v1/geolocate
+url=https://api.beacondb.net/v1/geolocate
 # Contributing back
 submit-data=true
-submission-url=https://beacondb.net/v2/geosubmit
+submission-url=https://api.beacondb.net/v2/geosubmit
 # I doubt this is used, but explicitly set just in case of it suddenly
 # becoming $(whoami)
 submission-nick=geoclue