Keep using pysnmp-lextudio to avoid conflict installation

The pysnmp-lextudio version is more recent and maintained, we should
keep using that for the time being to avoid conflicts of
installation with ironic, while using simple pyasn1.

Change-Id: Icb6e7779100b676685e227e225fde5c392141333

This reverts commit 56c50734.

Change-Id: Ie72b2a955d49cd6d1d5a802d499dd45cea9a518e

Fix for power on failure

Closes: 2021995
Change-Id: Id98474c334840ecc86371aa6b6395f7b4d6b1714

Update antelope for sushy version and constraints file branch

The pysnmp library is not maintained since 4 years now and it's
incompatible with recent libraries like pyasn1.
Its fork pysnmp-lextudio is regularly maintained, we should move
to that.
For more info see https://github.com/etingof/pysnmp/issues/429

Change-Id: Ic37805b39054b1d6a4a4c69a8faf57b512d920a0

Change-Id: I89ce8f6ec137a0c362e8291fa73b0a4f6ca5fd03

Change-Id: I9834d810a4125b40584aa896e707fcaf2794054a

Change-Id: If8df3833e66f02b4fbb51cf8d19c26197bfe997e

    Python 3.11 (Closes: #1030469).

Also fix unit test for sushy update.

Change-Id: I9548e1685f240cc7e559d9f029071099b2191068

Proliantutils has a pattern of testing internal calls inside of
the Sushy library. This has the unfortunate side effect of becoming
broken as bugs and related issues are fixed.

Fixes the check on a response which upstream sushy has discovered
has become sensitive on several vendors where eTags must be utilized
to ensure a reliable and correct response from the BMC.

Related-Bug: #1976555
Change-Id: I6b802fbb6a3f93f67269c141cad02b58ccd2d3ac

CSR releated changes

Change-Id: Ib586139ad60cafa9ac474fa9136ce52483f4d680

Change-Id: Idb1d362bc890afbc6bd6b4aca42a5eed841d1b35

Change-Id: I89c930b2c4f7363821441b17ff29755b559061db

Change-Id: Id18e39e174b19478cac723994e7e18aa1e30be13