Future Implementations for classes - Measure, Money, and Date

[ngachchi]

What does this PR do ?

This pull request introduces enhanced functionality for three classes: Measure, Money, and Date. These improvements are designed to increase usability and flexibility in handling various scenarios related to measurement units, currency transactions, and date manipulations.

Key Changes:

Measure Class:

• Introduced the "into" operator and added support for various measurement types, enabling users to define and manipulate custom units tailored to their needs.

Money Class:

• Implemented functionalities for minor currencies, allowing for more precise financial calculations (e.g., handling cents and pennies).

Date Class:

• Developed a flexible date range functionality, allowing users to manage periods confidently, including start and end dates.
• Integrated support for different eras (e.g., BC/AD, fiscal years) to ensure compatibility with both historical and future date representations.

Before your PR is "Ready for review"

Pre checks:

• Have you signed your commits? Use git commit -s to sign.
• Do all unittests finish successfully before sending PR?
  1. pytest or (if your machine does not have GPU) pytest --cpu from the root folder (given you marked your test cases accordingly @pytest.mark.run_only_on('CPU')).
  2. Sparrowhawk tests bash tools/text_processing_deployment/export_grammars.sh --MODE=test ...
• If you are adding a new feature: Have you added test cases for both pytest and Sparrowhawk here.
• Have you added __init__.py for every folder and subfolder, including data folder which has .TSV files?
• Have you followed codeQL results and removed unused variables and imports (report is at the bottom of the PR in github review box) ?
• Have you added the correct license header Copyright (c) 2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved. to all newly added Python files?
• If you copied nemo_text_processing/text_normalization/en/graph_utils.py your header's second line should be Copyright 2015 and onwards Google, Inc.. See an example here.
• Remove import guards (try import: ... except: ...) if not already done.
• If you added a new language or a new feature please update the NeMo documentation (lives in different repo).
• Have you added your language support to tools/text_processing_deployment/pynini_export.py.

PR Type:

• New Feature
• Bugfix
• Documentation
• Test

If you haven't finished some of the above items you can still open "Draft" PR.

[mgrafu]

That is correct, but we removed the cardinal's final graph to add only digits, teens, ties, hundreds, and thousands, and it might make sense to do the same for decimals instead of using the final graph without negatives there as well

[ngachchi]

That is correct, but we removed the cardinal's final graph to add only digits, teens, ties, hundreds, and thousands, and it might make sense to do the same for decimals instead of using the final graph without negatives there as well

The decimal.final_graph contains the logic for the fractional part, which is essential and cannot be omitted.

[mgrafu]

That is correct. Please make sure to include logic for thr fractional part in your trimmed down version of it here

[ngachchi]

That is correct. Please make sure to include logic for thr fractional part in your trimmed down version of it here

I have incorporated the necessary decimal graph to eliminate the use of decimal.final_graph.

[mgrafu]

LGTM -- waiting to be able to run CI tests in the correct branch