Don't lose optional chaining with objectAt in autofix for no-array-prototype-extensions rule

[52052100]

Summary

Add optional chaining support to objectAt auto-fixer.

Detail

Right now the objectAt auto-fixer in no-array-prototype-extensions will remove the optional chaining operator(?.). So this PR will use callExpressionNode.callee.optional to check the optional chaining use case and keep the optional chaining operator.

For example, the following template
const response = this.demoResponses?.objectAt(questionIndex);

Before:
const response = this.demoResponses[questionIndex];

After:
const response = this.demoResponses?.[questionIndex];

Testing Done

Add two new test cases to check the optional chaining use case.
All test cases passed.

[bmish]

Do you think this is an issue with any of the other functions in the autofixer?

[52052100]

Do you think this is an issue with any of the other functions in the autofixer?

yeah, had a discussion with @tgvrssanthosh , this issue might be not specific to objectAt but across all of them. Need to do some tests. We can have more general support for optional chaining use cases.

[bmish]

Feel free to use fix the issues with the other functions in separate PRs or in the same PR, up to your preference. For the next PR you could try to address multiple functions if you want. Looks like this PR is almost finished except you need to fix lint (and I recommend enabling trim trailing whitespace in your editor).

[52052100]

Feel free to use fix the issues with the other functions in separate PRs or in the same PR, up to your preference. For the next PR you could try to address multiple functions if you want. Looks like this PR is almost finished except you need to fix lint (and I recommend enabling trim trailing whitespace in your editor).

Sure, no problem! I will try to fix other functions in separate PRs to make sure don't break the function. Thanks for the suggestion! Just updated the code format and push.

[bmish]

Thanks a lot!