feat: Add FormattedValue support for f-string formatting

[SanjayUG]

Title

feat: Add FormattedValue support for f-string formatting

Description

What is this PR

• Addition of a new feature

Why is this PR needed?

This PR is needed to enhance the functionality of f-string formatting by adding support for formatted values, which allows for more flexible and powerful string formatting.

What does this PR do?

This PR introduces the following changes:

• Adds FormattedValueKind to the ASTKind enum.
• Implements the FormattedValue class for handling f-string formatted values.
• Adds transpiler support for formatted values.
• Adds test cases to ensure correct handling of formatted values.

References

#202

How has this PR been tested?

New test cases have been added to cover the handling of formatted values in f-strings. These tests ensure that the new functionality works as expected and that no existing functionality has been affected.

Is this a breaking change?

This PR does not break any existing functionality. It only adds new functionality for f-string formatted values.

Does this PR require an update to the documentation?

Yes, the documentation has been updated to reflect the changes and the addition of the new feature.

Checklist:

• The code has been tested locally
• Tests have been added to cover all new functionality
• The documentation has been updated to reflect any changes
• The code has been formatted with pre-commit

[xmnlab]

Hi @SanjayUG , thanks for working on that!
Instead of FormattedValue, it would be better if we call it as LiteralFormattedString, we don't need to keep the same name used by Python, and it would be better to keep the consistency with the other classes.

[github-actions]

This pull request has been marked as stale because it has been
inactive for more than 5 days. Please update this pull request
or it will be automatically closed in 5 days.

[SanjayUG]

Hi @SanjayUG , thanks for working on that! Instead of FormattedValue, it would be better if we call it as LiteralFormattedString, we don't need to keep the same name used by Python, and it would be better to keep the consistency with the other classes.

Thank You for the feedback, I would be sighting it.

[github-actions]

This pull request has been marked as stale because it has been
inactive for more than 5 days. Please update this pull request
or it will be automatically closed in 5 days.

[xmnlab]

closing this pr as stale. @SanjayUG if you still want to work on that, please ping us on discord to check if no one else has started to work on that.
thanks