Ignore some warnings

[timokau]

Description

We do not have control about any of these warnings except the last one.
And that one is harmless in a testing context.

Maintaining a list of these filters is cumbersome. I wish there was some
way to automatically ignore all warnings caused by third party code, but
unfortunately I don't think there currently is. I've opened
pytest-dev/pytest#6191
to discuss this.

I still think it is worthwhile to filter these warnings, because
otherwise they drown out those warnings that are actually relevant.

How Has This Been Tested?

Ran all tests.

Does this close/impact existing issues?

Related to #59.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.

[timokau]

Remaining warnings are the scikit-optimize warning that cannot currently be filtered, #72, #73 and #74.

[coveralls]

Pull Request Test Coverage Report for Build 577

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 40.548%

---

Totals
Change from base Build 574:	0.0%
Covered Lines:	9346
Relevant Lines:	23049

---

💛 - Coveralls

[kiudee]

It’s a good idea to silence some of the warnings out of our control.
Other than the two typos, this looks ready to be merged.

[timokau]

Great! I've fixed the typos.