feat: add backend BYOK support for GlobalPing integration

[hybrid-zz]

Added backend support for admins to provide their own GlobalPing API key, aligning the implementation closely with the existing Google PageSpeed key integration. When a key is saved, the server automatically attaches an Authorization header to each GlobalPing request, otherwise it will fallback on anonymous checks.

As an additional improvement, I exposed an admin-only settings route that provides status information related to the configured API key:

1. Whether the key is valid or rejected
2. Remaining credits associated with the key
3. Remaining rate limit (per hour, according to the GlobalPing API documentation)

This information could later be used to further enhance the integration. For example:

• Defining a threshold for notifications
• Creating an incident when credits are low or exhausted

My apologies for the previous PR. I misunderstood your request and thought you wanted two separate PRs: one for BYOK and one for Granular Node Control. Don't mind the commits, lol I made a mess.

Partially Fixes #3413

Please ensure all items are checked off before requesting a review. "Checked off" means you need to add an "x" character between brackets so they turn into checkmarks.

• (Do not skip this or your PR will be closed) I deployed the application locally.
• (Do not skip this or your PR will be closed) I have performed a self-review and testing of my code.
• I have included the issue # in the PR.
• I have added i18n support to visible strings (instead of <div>Add</div>, use):

const { t } = useTranslation();
<div>{t('add')}</div>

• I have not included any files that are not related to my pull request, including package-lock and package-json if dependencies have not changed
• I didn't use any hardcoded values (otherwise it will not scale, and will make it difficult to maintain consistency across the application).
• I made sure font sizes, color choices etc are all referenced from the theme. I don't have any hardcoded dimensions.
• My PR is granular and targeted to one specific feature.

[ajhollid]

Looks good for the most part, some minor changes required. Thanks for your contribution!

[ajhollid]

This makes a DB call on every globalping request, that's a lot of overhead.

Let's cache the key with a reasonable invalidation period so we don't have to keep querying the DB

[ajhollid]

Tihs appears contradictory, as these values are both validated as nullable in the validation:

const globalpingLimitsResponseSchema = z.object({
	rateLimit: z
		.object({
			measurements: z
				.object({
					create: z
						.object({
							remaining: z.number().nullable().optional(),
						})
						.optional(),
				})
				.optional(),
		})
		.optional(),
	credits: z
		.object({
			remaining: z.number().nullable().optional(),
		})
		.optional(),
});

If they are expected to be null, then this should not be an error but an unknown response.

If they are not expected to be null, then let the validation handle this and remove the nullable