fix: refactor api_new_meeting_registration. Fixes #7608

[rpcross]

• change to use JSON payload
• handle multiple records in one request

[rpcross]

I am working on tests for this. Using a JSON payload means the existing require_api_key decorator won't work. Assuming JSON payload is the way to go, are there other precedents for checking API key? Function can do it's own validation, or can update decorator.

[jennifer-richards]

are there other precedents for checking API key?

datatracker/ietf/api/ietf_utils.py

Lines 27 to 46 in b5ab4b6

	def requires_api_token(func_or_endpoint: Optional[Union[Callable, str]] = None):
	"""Validate API token before executing the wrapped method
	Usage:
	* Basic: endpoint defaults to the qualified name of the wrapped method. E.g., in ietf.api.views,
	@requires_api_token
	def my_view(request):
	...
	will require a token for "ietf.api.views.my_view"
	* Custom endpoint: specify the endpoint explicitly
	@requires_api_token("ietf.api.views.some_other_thing")
	def my_view(request):
	...
	will require a token for "ietf.api.views.some_other_thing"
	"""

is what we've started using for datatracker. This uses the X-Api-Key header to store a shared secret and keeps the auth concerns out of the API itself.

[rjsparks]

@rpcross This may have fallen into the cracks because of 120?