text: Title: Robot Framework does not run outside Windows if `signal.setitimer` is not available (affects e.g. Pyodide)
  Body: As described by @Snooz82  in Slack:
  
  > Pyodide 0.23 and newer runs Python 3.11.2 which officially supports WebAssembly as a [PEP11 Tier 3](https://peps.python.org/pep-0011/#tier-3) platform. [#3252](https://github.com/pyodide/pyodide/pull/3252), [#3614](https://github.com/pyodide/pyodide/pull/3614)
  > 
  > That causes incompatibility to Robot Framework… :sob:
  > RF uses setitimer and this seems not be included anymore, because it never worked on JavaScript…
  > That means we can not update to Pyodide 0.23.0 from March 30 2023…
  > current Version is 0.25.0
  > 
  > I updated it on the code playground now from 18.1 to 22.1 which caused RF 3.1 to die, due to missing python 3.10 support.
  > We could refactor the code so, that depending on the selected Robot Version we do use a different Pyodide Version.
  > And in the next Release of Robot Framework, we could actively check if we can support running on newest Pyodide version.
  > Maybe that mean, that some timer signals are not working, but i think that would be ok.
  > Pekka: if you think there is a possibility to patch robot/running/timeouts/posix.py so that RF could still live without it, this would be an option too.
  
  When I tried Robot Framework in a Jupyter Lite Notebook using Pyodide, I received the error below:
  
  `ImportError: cannot import name 'setitimer' from 'signal' (/lib/python311.zip/signal.py)`
  