Restrict partner colors by server membership

[Rocked03]

Turns out we never actually implemented this, we just left the allColorsGlobal switch set to true and called it a day

Canvas-Web/packages/backend/src/services/pixelService.ts

Lines 74 to 78 in 67b19c7

	if (!color.global && !config.allColorsGlobal) {
	throw new ForbiddenError(
	`Partnered color with ID ${colorId} is not allowed from web client`,
	);
	}

We already get their server membership via auth, we just need to check against it. It's not high stakes so we shouldn't really need to validate the auth in the backend every time (ratelimits 😒), but it's probably worth instead keeping medium-length cache records that re-validates periodically

[Rocked03]

lol thanks @stijnvdkolk for making me aware of this when I was looking at #555, that's fully a massive oversight that frankly has slipped my mind for the past couple years

[Rocked03]

tbh we should be fine to keep the switch flipped on but it's good functionality to, y'know, actually have working

[stijnvdkolk]

@Rocked03 want me to include this in my current PR or pick this up separately?

[Rocked03]

Idm, up to you

Could always stack the branches

[stijnvdkolk]

Yeah probs will do that

[Rocked03]

Additional thought - perhaps we add some sort of "refresh/recheck server membership" button in the user page in any cases where they may join a server but the canvas web doesn't immediately update