feat: autofix for prefer-logical-properties

[k-yle]

Prerequisites checklist

• I have read the contributing guidelines.

AI acknowledgment

• I did not use AI to generate this PR.
• (If the above is not checked) I have reviewed the AI-generated content before submitting.

What is the purpose of this pull request?

IDE suggestions for the prefer-logical-properties rule

What changes did you make? (Give an overview)

added a fixer to all 3 cases.

Related Issues

none

Is there anything you'd like reviewers to focus on?

[eslint-github-bot]

Hi @k-yle!, thanks for the Pull Request

The pull request title isn't properly formatted. We ask that you update the pull request title to match this format, as we use it to generate changelogs and automate releases.

• The commit message tag wasn't recognized. Did you mean "docs", "fix", or "feat"?
• There should be a space following the initial tag and colon, for example 'feat: Message'.

To Fix: You can fix this problem by clicking 'Edit' next to the pull request title at the top of this page.

Read more about contributing to ESLint here

[DMartens]

Thank you for the PR.
In the future please open an issue before changing rules, so we can discuss the potential changes.
In this case the rule seems to should have a fixer (meta.fixable is set) but the fixer was not implemented. The corresponding stylelint rule property-layout-mappings also provides an autofix.
Are there cases where an autofix would be unsafe?

[k-yle]

an automatic fix is definitely not safe, it must be a manually reviewed suggestion.

Even if you design for RTL from day 1, there are always cases where you want something to be fixed to the the same side, regardless of LTR or RTL.

[DMartens]

I agree, in the case the rule is enabled without the underlying mindset, it can cause breakages.
Can you please remove meta.fixable property, otherwise the changes LGTM.