Add Fleet server configs for new Apple VPP metadata endpoints

[marko-lisica]

Related to:

• Add software: custom App Store (VPP) apps #32461

We decided to ship this in 4.81. This PR removes it from docs-v4.80.0: #38626

[marko-lisica]

Hey @noahtalerman, I tooka pass at the server config names here.

@iansltx already added a config for App Store region, and I took a pass at explaining it. I think since we have a feature request (#34189) for this, we should work on this in a separate story, to think a little bit more about this.

Most apps are global, so they typically appear regardless of the region you specify. However, some apps are restricted to specific countries, requiring you to select a different region. I think we still need to understand this use case better before committing to its release.

[noahtalerman]

Suggested change

	### mdm.apple_vpp_app_metadata_api_proxy
	### mdm.apple_vpp_app_metadata_api_proxy

@marko-lisica why do we need this? To keep the configuration surface consistent and smaller/simpler to use, I think let's just add the mdm.apple_vpp_app_metadata_api_bearer_token config. If it's specified, Fleet talks directly to Apple.

[iansltx]

If we revise that behavior rather than just config values it'll bump up complexity a bit for something for which the dev sprint completed a week and a half ago.

Doable, but figured I'd flag since if this is still intended for 4.80 my plan was to be OOO for the rest of the week starting tomorrow, and we're getting to the point where this could be the thing holding up 4.80 GA.

[noahtalerman]

I think it's worth the delay. We want to revise this to be reduce config surface.

Regarding timing, I hear you. I started a thread in #g-software to discuss this expedited drafting: https://fleetdm.slack.com/archives/C086V2QK76X/p1769013732377589