Add feature to enable using W; as a wash scheme - needed for DiTi evos.

[NikolasvdEichen]

As discussed in the open issue, this is a change to enable using the right wash scheme for diti evos that strictly require an "W;" as a wash scheme and do not cope with "W1;" or any other number.
Question: Do you bump the version number manually or automatically for the pypi build?

[github-actions]

Thank you for your submission, we really appreciate it!

Like many open-source projects we ask that you sign our Contributor License Agreement before we can accept your contribution.
To sign, please post two separate comments based on the following templates 👇

1. Comment:

---

- [ ] The JuBiotech maintainers know my real name.

At least one of the following two applies:

- [ ] The JuBiotech maintainers know my current employer.

- [ ] I am *not* making this contribution on behalf of my current employer.

---

2. Comment:

   ---

   I have read the CLA Document and I hereby sign the CLA.

   ---

   _{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}

[NikolasvdEichen]

- [ ] The JuBiotech maintainers know my real name.

I do not know what I am supposed to do tbh - Michael knows my real name and my current employer.

[michaelosthege]

- [ ] The JuBiotech maintainers know my real name.

I do not know what I am supposed to do tbh - Michael knows my real name and my current employer.

Just copy the code block from the first bot comment, tick the boxes (yes, we know your name, and also your current employer), and post it as a comment.

Then post a second comment with the text "I have read the CLA Document and I hereby sign the CLA." and the bot will re-run and approve.

[codecov]

Codecov Report

Attention: Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 95.41%. Comparing base (79a4410) to head (2331031).
Report is 45 commits behind head on master.

Files with missing lines	Patch %	Lines
robotools/worklists/base.py	80.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master      #78      +/-   ##
==========================================
+ Coverage   95.37%   95.41%   +0.04%     
==========================================
  Files          18       19       +1     
  Lines        1102     1156      +54     
==========================================
+ Hits         1051     1103      +52     
- Misses         51       53       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[NikolasvdEichen]

- [ ] The JuBiotech maintainers know my real name.

I do not know what I am supposed to do tbh - Michael knows my real name and my current employer.

Just copy the code block from the first bot comment, tick the boxes (yes, we know your name, and also your current employer), and post it as a comment.

Then post a second comment with the text "I have read the CLA Document and I hereby sign the CLA." and the bot will re-run and approve.

Hi,
problem: I can not do any virtual signing of a CLA without including our legal department, which will probably take a few weeks or even months - which is way too long.
Is there any other way to do this without me having to chase lawyers for weeks?

[michaelosthege]

Sure, I will just make a new PR with the equivalent feature ;)

---

Independent of that, you're welcome to attempt to get a go from your legal department just in case you're making more contributions in the future.

FZ Jülich's legal department was OK with the bot-assisted, digital workflow, but we can also take handwritten signatures on the CLA document. We can manually commit a PDF to the behind-the-scenes repository where the CLA bot also makes commits to document digital signatures.
We can continue this by email if you like.