Analyze uint{32,64} compatibility with OTTL

[felixge]

OTTL seems to only support int64 and float64 as numeric data types (source). The profiling signal uses uint32 and uint64 in a few places:

Message.field	Type
Profile.duration_nano	uint64
Profile.dropped_attributes_count	uint32
Mapping.memory_start	uint64
Mapping.memory_limit	uint64
Mapping.file_offset	uint64
Location.address	uint64

This issue exists to decide if this is a problem that needs addressing, and if yes, how. This was first raised at the 2026-03-12 Profiling SIG meeting (see notes).