VATPRC TMA Update

[RudiZhang]

Description

• TMA boundaries re-defined

Motivation and Context

• match ATC sectors, add necessary sub-sector

How to prove the effect of this PR?

Is this a breaking change?

• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• My change or addition follow the formatting standard of the project.
• I am on the list of approved contributors.

[kmoberg]

This is a pretty massive pull-request changing a lot of files. I know it's not easy, but can you help make this easier for us by documenting what to expect things to look like, according to the policy on How to submit a pull request? That would make our job of verifying this a heck of a lot easier. @RudiZhang

[RudiZhang]

This is a pretty massive pull-request changing a lot of files. I know it's not easy, but can you help make this easier for us by documenting what to expect things to look like, according to the policy on How to submit a pull request? That would make our job of verifying this a heck of a lot easier. @RudiZhang

only ZBAA_F ZBAD ZSSS_W ZSSS_S ZWWW_E ZSSS_F ZSSS_PD will be added fully new. All others are re-defined boundaries. The screenshots below are from Aero-Nav which we used for sectorfiles. Exactly the same as this PR.

[RudiZhang]

There are some screenshots for this PR