directly use UAT messages instead of uat2esnt

[justin4046]

ive been running this for about a week with both encapsulated and dump978 messages with no issues. only minor changes to tar1090 for the new addr type

[wiedehopf]

there is a lot of infrastructure that relies on the conversion.
as in the aggregators.

so this change would break that.

i guess they can update readsb ... but still it's a pretty breaking change.

[justin4046]

i think it should be fine as long as the aggregators at least support encapsulated uat. every uat feed would need to be updated anyway to send uat messages instead of esnt, which would just be put through uat2esnt once it got to the aggregator.
i guess there should be an option to pick between this and uat2esnt, but im not as familiar with all that

[wiedehopf]

well updating clients before updating aggregators is a very real possibility.

plus this breaks the regular beast output someone might be rely on with the beast out going into VRS or similar.
and the regular beast output also can't have arbitrary beast message types added as that can cause issues in receiving applications that only understand standard beast.

until i can think of a solution for this, i won't take this PR or make a similar change.
i'll leave the PR open but i don't really want to use it.