Support payload normalization

[johanstokking]

Summary

Closes #5429
References TheThingsNetwork/lorawan-devices#395

Changes

• This adds normalized_payload to upstream messages
• Also includes initial parsing of normalized payload per the draft schema (see referenced Device Repository PR)

Testing

Unit testing and local integration testing

Regressions

None expected

Notes for Reviewers

Skip the first commit; all lint warning removals are squashed in there

This includes some commits from #5727 to show non-LoRa data rates in the event preview

@kschiffer please review console: commit only

We can probably do improve, but this is already pretty cool:

Checklist

• Scope: The referenced issue is addressed, there are no unrelated changes.
• Compatibility: The changes are backwards compatible with existing API, storage, configuration and CLI, according to the compatibility commitments in README.md for the chosen target branch.
• Documentation: Relevant documentation is added or updated.
• Changelog: Significant features, behavior changes, deprecations and fixes are added to CHANGELOG.md.
• Commits: Commit messages follow guidelines in CONTRIBUTING.md, there are no fixup commits left.

[adriansmares]

I like the direction in which this is going.

Now that the uplink payload formatter parameter encapsulates two functions at once, should we consider increasing the character limit, or do we keep the one we have so far ?

[johanstokking]

Now that the uplink payload formatter parameter encapsulates two functions at once, should we consider increasing the character limit, or do we keep the one we have so far ?

Let's not do that until we run into problems. I think we're already quite generous in the Device Repository with 64KB.

Inline codecs in The Things Stack have a lower limit, but since we support detecting whether the payload is already normalized, what is really needed is that codec developers just return normalized payload going forward.

[johanstokking]

@adriansmares this is ready for another full pass

You can skip the first commit; all lint warning removals are squashed in there, no functional changes otherwise

[adriansmares]

Webhook template store schema (the YAML files that describe the templates) require an update with the new message type too. See

lorawan-stack/pkg/applicationserver/io/web/templates.go

Lines 225 to 236 in 6db9aff

	type webhookTemplatePaths struct {
	UplinkMessage *string `yaml:"uplink-message,omitempty"`
	JoinAccept *string `yaml:"join-accept,omitempty"`
	DownlinkAck *string `yaml:"downlink-ack,omitempty"`
	DownlinkNack *string `yaml:"downlink-nack,omitempty"`
	DownlinkSent *string `yaml:"downlink-sent,omitempty"`
	DownlinkFailed *string `yaml:"downlink-failed,omitempty"`
	DownlinkQueued *string `yaml:"downlink-queued,omitempty"`
	DownlinkQueueInvalidated *string `yaml:"downlink-queue-invalidated,omitempty"`
	LocationSolved *string `yaml:"location-solved,omitempty"`
	ServiceData *string `yaml:"service-data,omitempty"`
	}