CI: fetch packages info if server tests fail

[tal66]

Hi, this closes #2777.
I used pip list --outdated. So basically, this script is only necessary because of the 'past X days' requirement.

see my (other) experimental branch for demo run that fails on purpose: https://github.com/tal66/elyra/actions/runs/2477060776

[elyra-bot]

Thanks for making a pull request to Elyra!

To try out this branch on binder, follow this link:

[ptitzler]

LGTM! Very nice work, thank you for your contribution and awesome turnaround time!

[ptitzler]

General question: currently the output is sorted by package name, which makes perfect sense if one wants to quickly check if one of the 'usual suspects' (packages that have broken Elyra in the past) has changed:

Newer version for <google-api-python-client>:
 - released 2.50.0  2022-06-07	(>)
 - current  1.12.11

Newer version for <google-auth>:
 - released 2.7.0  2022-06-07	(>)
 - current  1.35.0

Newer version for <google-cloud-core>:
 - released 2.3.1  2022-06-09	(=)
 - current  2.3.1

Newer version for <google-cloud-storage>:
 - released 2.4.0  2022-06-08	(>)
 - current  1.44.0

Newer version for <ipykernel>:
 - released 6.13.1  2022-06-06	(=)
 - current  6.13.1

Newer version for <jupyter-client>:
 - released 7.3.4  2022-06-08	(=)
 - current  7.3.4

Newer version for <jupyter-server>:
 - released 1.17.1  2022-06-07	(=)
 - current  1.17.1

Newer version for <jupyterlab>:
 - released 3.4.3  2022-06-07	(=)
 - current  3.4.3

Newer version for <kfp-server-api>:
 - released 1.8.2  2022-06-10	(=)
 - current  1.8.2

Newer version for <networkx>:
 - released 2.8.3  2022-06-04	(>)
 - current  2.6.3

Newer version for <notebook>:
 - released 6.4.12  2022-06-07	(=)
 - current  6.4.12

Newer version for <pipenv>:
 - released 2022.6.7  2022-06-07	(>)
 - current  2020.11.15

Newer version for <pylint>:
 - released 2.14.1  2022-06-06	(=)
 - current  2.14.1

Newer version for <requests>:
 - released 2.28.0  2022-06-09	(=)
 - current  2.28.0

Newer version for <watchdog>:
 - released 2.1.9  2022-06-10	(=)
 - current  2.1.9

However, since we are also running automated daily tests (e.g. https://github.com/elyra-ai/elyra/actions/runs/2478594976) where probably sorting the output by the most recent change date (in descending order) might be a bit more useful. Would be interested in hearing what other think.

[ptitzler]

We've discussed this in todays's dev meeting and decided to leave the report output as is for now.