* Revert "Metadata updates for release 8.12.47 (#2754)"

This reverts commit 299e3c53da.

* Fix carrier and geocoding data file paths

* Added new classes with behavior from MetadataManager & MetadataSource

* Replaced MetadataManager usages with new classes

* New PrefixDataIOHandler which packs data into a jar

* Added mockito-core jar to lib folder

* Added mockito-all jar to lib folder and updated tests to not use junit4 annotations

* Fixed prefix generation entry points

* Specific exception for missing metadata cases

* Small change in checking missing metadata cases

* [maven-release-plugin] prepare release v8.12.46

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.45

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.44

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.43

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.41

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.40

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.39

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.38

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.37

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.36

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.35

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.34

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.33

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.31

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.30

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.29

* [maven-release-plugin] prepare for next development iteration

Earlier, AYTF is adding additional CC when returning unformatted result - for cases where the input digits are dropped for formatting. Eg: MX case: "+5213314010666" => "+52 +5213314010666". b/183053929

Now we. are proactively ensuring that no formatting is applied, where a format is chosen that would otherwise have led to some digits being dropped.

Why the input digits are dropped:
- In MX, the mobile token (1) is no more used, so when it is present in input, the formatted result should not contain it.
- However when AYTF, we should not be removing the input digits on the fly.
- More details in cl/373115460 and b/183053929

* [maven-release-plugin] prepare release v8.12.28

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.27

* [maven-release-plugin] prepare for next development iteration

* [maven-release-plugin] prepare release v8.12.26

* [maven-release-plugin] prepare for next development iteration