fix: produce valid code when when fixing properties accessed with square brackets

[G-Rath]

Very minor (I really don't think anyone is accessing properties this way) but it's technically a bug - I realised afterwards that the alternative is to do:

fixer.replaceTextRange(
  [matcher.node.object.range[1], matcher.node.range[1]],
  `.${...}`,
),

which ensures the whole accessor is removed correctly making it safe to not use quotes - I'm not fussed which fix we actually do, but felt this helper was slightly better by way of being more readable 🤷

We could be using it in no-deprecated-functions too except that technically isn't using a node of type AccessorNode so have left it as-is for now since it technically should be refactored anyway to use the new jest function parser.

[github-actions]

🎉 This PR is included in version 26.4.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀