Flake8: Drop ignore of issue A003

[cclauss]

Describe your change:

• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Documentation change?

Checklist:

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized.
• I know that pull requests will not be merged if they fail the automated tests.
• This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
• All new Python files are placed inside an existing directory.
• All filenames are in all lowercase characters with no spaces or dashes.
• All functions and variable names follow Python naming conventions.
• All function parameters and return values are annotated with Python type hints.
• All functions have doctests that pass the automated testing.
• All new algorithms include at least one URL that points to Wikipedia or another similar explanation.
• If this pull request resolves one or more open issues then the commit message contains Fixes: #{$ISSUE_NO}.

[CaedenPH]

Personally, I prefer attributes such as next and prev to next_ and prev_
Especially when it comes to set and put, because they are different concepts.
I don't see a problem with globally ignoring A003

[dhruvmanila]

@cclauss I agree with @CaedenPH on this and was discussed earlier as well. A003 is a false positive and is supposedly going to be disabled by default in the plugin itself. I suggest to revert this change.

[cclauss]

@gforcada Your sense of this pull request? Does A003 generate false positives? Should we revert?

[gforcada]

If my opinion is asked, here is is given 😄 : I very much prefer to keep A003 enabled on the plugin itself, and let each user decide if it's useful or not. For my projects I very much prefer not to use builtins even on A003 cases, that my personal preference. Fortunately flake8 has a powerful configuration system and you probably are already configuring some bits of it anyway. I will not get offended if someone ignores A003 😃