no-tautology-expression should check property access expressions

[DerZyklop]

Rule Suggestion

Is your rule for a general problem or is it specific to your development style?
General problem.

What does your suggested rule do?
Check if there is a duplicate in a if statement.

List several examples where your rule could be used

const foo = true;
if (foo && foo) { // <- Tslint error/warning at second foo
	console.log('Second foo check was unneccessary.');
}

Additional context
Here an example from real code from my project:

if (this.urlParam.start && this.urlParam.start) {
	...
}

Problem was: The code-block should only be executed if a .start and .end was set. I accidentally checked .start and .start. The suggested rule would have prevented that.

[JoshuaKGoldberg]

@DerZyklop agreed! The first foo && foo case should be covered by the new no-tautology-expression rule. As for this.urlParam.start && this.urlParam.start, it looks like it's not yet covered by the rule's test cases, but should be.

[JoshuaKGoldberg]

☠️ TSLint's time has come! ☠️

TSLint is no longer accepting most feature requests per #4534. See typescript-eslint.io for the new, shiny way to lint your TypeScript code with ESLint. ✨

It was a pleasure open sourcing with you all!

[JoshuaKGoldberg]

🤖 Beep boop! 👉 TSLint is deprecated 👈 (#4534) and you should switch to typescript-eslint! 🤖

🔒 This issue is being locked to prevent further unnecessary discussions. Thank you! 👋