Processing level ID

[lavanya3k]

Description of the PR - This is a PR request to address ticket #320. In the processing level ID, we want to include additional levels as per the ESDS guidance. The actual list of processing levels consists of the following.
[Not Provided, 0, 1, 1A, 1B, 1C, 1T, 2, 2A, 2B, 2G, 2P, 3, 3A, 4, NA]. See the reference https://gcmd.earthdata.nasa.gov/kms/concepts/concept_scheme/ProductLevelId?format=json

Code changes - The code changes were made in the rules_override.json and check_messages_override.json. Further, we updated the outdated files in the test_downloader.py and schema_validator.py. There was an outdated imports DraftValidator, and this has to be updated before every commit. The final code is test by running pytest, and the run was successful before committing the code changes.

To reproduce - Use the following files for testing
C1708952717-CDDIS --format umm-c (Processing level ID: 1)
C1537294867-CDDIS --format umm-c (Processing level ID: 2)
C3241567254-CDDIS --format umm-c (Processing level ID: 1)

Expected output - You will not see any error for ProcessingLevel/Id in the console. If incorrect processing level ID is provided, you will have the following output

[FBayat021]

Here are the corresponding concept IDs available in EDS for the collections that initially were provided from the MMT:

PREFIRE_SAT2_AUX-MET: C3457546411-LARC_CLOUD
PREFIRE_SAT1_AUX-SAT_R01 (short name: PREFIRE_SAT1_AUX-SAT): C3518594654-LARC_CLOUD

Great work @lavanya3k

[lavanya3k]

Testing on the dev branch: The processing level ID worked for the following collection.

[lavanya3k]

Tested in dev for the above collection ID, fake file, and test file.

Expected output: