Updated revision date to conform to the rule in 32.160 clause 6.2.1.13

In order to avoid reusing the same revision date in multiple releases, when a new YANG module revision is needed the revision date shouldbe set as follows. Instead of setting the exact revision date when the module was last edited, the date nearest to that day that is not in the future and that follows the rule below should be used.
When divided by 6, the day in the date should have the same remainder as the release number: (DAY modulo 6 == releaseNumber modulo 6).

Merge branch 'Rel16_CR_TS_28.541_Update_stage3_for_allowed_value_ueAccProbabilityDist' into 'Integration_Rel16_SA5_160_YANG'

Rel16_CR1501_TS_28.541_Update_stage3_for_allowed_value_ueAccProbabilityDist

See merge request !1664

Ts28.623 r16 cr0533 mdtplmn list yang

See merge request !1700

Merge branch 'Rel16_CR_TS28.541_Update_sector_equipment_and_antenna_function_definitions_yang' into 'Integration_Rel16_SA5_161_YANG'

Rel16 CR1551 28.541 Add sector equipment function and antenna function definitions

See merge request !1770

From Integration_Rel16_SA5_161_YANG into Rel-16

See merge request !1778