Add squishserver module

[ghost]

Added squishserver module to work with squishserver, which contains a dedicated class SquishServer. Added 3 methods to register AUTs:

• addAUT
• addAppPath
• addAttachableAut
  Also added a dedicated exception type "SquishserverError"

[pawtom]

For the completeness of the solution, it might be worth to add "remove" functions for the "add" functions:
*removeAUT
*removeAppPath
*removeAttachableAut

[pawtom]

With the recent changes, one can see the need to create a helper function, like:
_config_squishserver(config_option:str, params=[]) and extract common code from six created API functions into that one.

[pawtom]

Thanks for the recent changes, looks like a big improvement :)

[Adakar]

@pawtom could you please check my comments? :)

[Adakar]

In general it would be good to see squishserver details in logs. Lets imagine a situation where you have 2 squishservers. If you register different AUTs in each of them, the logs do not say which AUT was added to which squishserver

[Adakar]

Please read the comment I made last time

[pawtom]

@Adakar @EduardKaverinskyi
I'm wondering about the default port for squishserver.
def __init__(self, location=None, host="127.0.0.1", port=4322):
When squishserver is started automatically, this information is stored in SQUISHRUNNER_PORT environment variable.

So instead of doing something like that in the test script:
ss_port = os.environ.get("SQUISHRUNNER_PORT",4322) SquishServer(port=ss_port).addAttachableAut("abab", 5858, "localhost")

I would suggest that for the init method default values are:
for host
1. SQUISHRUNNER_HOST
2. localhost (if SQUISHRUNNER_HOST is not defined)

for port:
1. SQUISHRUNNER_PORT
2. 4322

What do you think?

[ghost]

I think that this idea is usable. I implemented it in the latest commit. Please check if it is as is suggested.

[Adakar]

@EduardKaverinskyi I'll not accept this PR without implementing more verbose log messages. It was mentioned twice already in this comment