Propagate verify=False from session to requests

[phinds1]

ref: https://forum.robotframework.org/t/how-to-make-requests-library-ignore-ssl-errors/6790

ref: #386

[lucagiove]

@phinds1 would be very useful a test that shows the bug and your PR that fixes the test.
This would speedup merging, otherwise I need to do it on my own.

[phinds1]

Are there unit tests somewhere? Or integration test framework that could have a broken SSL server added?

I didn't add a feature, its just a bug fix, so there should be no more or less test coverage.

[lucagiove]

An integration test is quite hard to develop in this case, I've on my list.
What could be done is an unit test to show the case where verify is not propagated properly.
It's not a matter of coverage but more a matter of process if a bug exists than a failing test can be written and then fixed.

[PaulBrandUWV]

This will break session less keywords (session is not defined in this case), and should not be necessary when the session has verify=False

[PaulBrandUWV]

I just tested this and it works as expected. Create session keyword by default sets verify to False

*** Settings ***
Library     RequestsLibrary

*** Variables ***
${url}    https://wrong.host.badssl.com/

*** Test Cases ***
Unverified GET on session request
    Create Session    test_session    ${url}
    GET on Session    test_session    /