Add prefer-reactive-destructuring rule

[tivac]

From the docs:

---

This rule triggers whenever a reactive statement contains an assignment that could be rewritten using destructuring. This is beneficial because it allows svelte's change-tracking to prevent wasteful redraws whenever the object is changed.

This svelte REPL example shows just how effective this can be at preventing bogus redraws.

<script>
  /* eslint svelte/prefer-reactive-destructuring: "error" */
  /* ✓ GOOD */
  $: ({ foo } = info)
  $: ({ bar: baz } = info)

  /* ✗ BAD */
  $: foo = info.foo
  $: baz = info.bar
</script>

[ota-meshi]

I've noticed that sometimes what the rule report doesn't lead to a reduction in render times.
I think the documentation might need to be fixed.

See #208 (comment)

[marekvospel]

The first letter should be lowercase to be consistent with existing rules. (see #218)

[baseballyama]

@tivac What are the remaining tasks of the PR? I can do the remaining tasks if you need.

[tivac]

@baseballyama Needs to be changed to a stylistic rule and any remaining comments need to be addressed (I think it's just capitalization nit?). Seems like either svelte has improved object access change tracking or my initial tests when I wrote these rules years ago were faulty 🤷🏻‍♂️ So this is really a style preference over a perf thing.

[baseballyama]

I checked this rule well, and now I understand this rule doesn't have an impact on rendering frequency.
And already ESLint can report destructuring through prefer-destructuring rule.

So I think even in terms of styling, I don't think we need to add this rule.
Now I tried to update this PR, but before that, I would like to clarify the needs of this rule.

[ota-meshi]

Thank you for the explanation.

And already ESLint can report destructuring through prefer-destructuring rule.
So I think even in terms of styling, I don't think we need to add this rule.

You are right. So I will close this PR.