- Added a check for parent nodes that are MemberExpressions
- If a parent node is a MemberExpression, the fixed number is now wrapped in
  parentheses to maintain correct syntax

This commit enhances the no-zero-fractions rule in the unicorn linter:

- Add support for scientific notation (e.g., 1e10, 1.e10)
- Improve handling of member expressions
- Introduce is_decimal_integer utility function
- Update test cases and snapshots to reflect new behavior
- Fix various edge cases in number formatting

These changes make the rule more robust and consistent with the original
ESLint implementation, especially for scientific notation and member
expressions.

…g and clarity

- Simplified the condition that checks for decimal integers within member expressions by removing unnecessary parentheses around the formatted string.
- Updated string formatting in `format_raw` function to use the shorthand `{variable}` syntax instead of `{}` with positional arguments.

- Handle special cases where a space is needed after certain keywords
  (return, throw, typeof) to prevent the number from being interpreted
  as a property access
- Add tests for these special cases
- Update existing tests to cover more scenarios

- Include 'void' in the list of keywords that require a space before
  the number to prevent misinterpretation as property access
- Add test cases for 'void' keyword scenarios

…o-zero-fractions` rule

- Removed the `is_decimal_integer` function and related `numeric.rs` utility, as it was no longer necessary.
- Simplified the `no-zero-fractions` rule by directly checking for non-dangling dots instead of using the removed utility.
- Updated the logic for fixing number formatting to remove redundant checks.

…s and decimal integers

- Refactored logic in the `NoZeroFractions` rule to ensure proper handling of cases where the numeric value is a decimal integer and part of a member expression.
- Added a clone of the format string to avoid mutating the original `fmt`.
- Introduced checks for `is_decimal_integer` and `is_member_expression` to better control the formatting of the fixed value.
- Updated test cases to cover additional scenarios, including fixing fractional values like `1.010.toFixed(2)` to `1.01.toFixed(2)`.

- Add TODO for more complex token checks and semicolon handling
- Prepare for special keyword cases requiring space after fixed value

- Add TODO for more complex token checks and