Remove backwards-compatibility for ENS mainnet requirement, let NameNotFound raise

[abhinay]

What was wrong?

• The code still contained a backward compatibility try/except block related to ENS name resolution, which was scheduled to be removed in Web3.py v7.
• This block prevented NameNotFound from being raised directly, instead converting it into InvalidAddress under certain conditions.

Related to Issue #
3580

Closes #
3580

How was it fixed?

• Removed the try/except NameNotFound block so that NameNotFound raises naturally.
• Updated the relevant test to ensure the new behavior.

Todo:

• Clean up commit history
• Add or update documentation related to these changes
• Add entry to the release notes

Cute Animal Picture

[reedsa]

Update: Answered my own question, this was discussed in the issue itself #3580

@fselmo @kclowes I think the code comment about updating for v7 was forgotten here. If the exception handling is removed and technically breaking, will this have to wait for the version 8?