Avoid false-positive with nested objects in GCI12

[utarwyn]

This PR improves the rule @creedengo/no-multiple-style-changes (GCI12) to avoid false-positives about nested objects. It also exclude non-literals to avoid reports when values are dynamic.

Fixes #72

[Copilot]

Pull Request Overview

This PR aims to improve the rule @creedengo/no-multiple-style-changes (GCI12) by preventing false-positives when nested objects are involved and by excluding non-literal assignments.

• Updated the test suite to include parser options and additional valid/invalid test cases for nested objects.
• Modified the rule implementation to derive a full object name using the new getNodeFullName helper.
• Updated the CHANGELOG to reflect these changes.

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
eslint-plugin/tests/lib/rules/no-multiple-style-changes.js	Added parser options and extra tests to cover nested object scenarios.
eslint-plugin/lib/rules/no-multiple-style-changes.js	Introduced getNodeFullName to support nested objects in style assignment checks.
CHANGELOG.md	Updated changelog for the new PR changes.

Comments suppressed due to low confidence (1)

eslint-plugin/lib/rules/no-multiple-style-changes.js:43

• The function getNodeFullName assumes that node has either a 'name' or 'property.name'. In cases where neither is available, this could lead to runtime errors. Consider adding safe checks to verify that these properties exist before using them.

names.unshift(node.name ?? node.property.name);

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud