Testing/jenkins integration

[fionnodonohoe-xlnx]

Main changes include:

• test support for 4 boards: Pynq-Z1, Alveo U250, Kria SOM KV260 and ZCU104
• added a bnn sanity test option (creates a single bitstream for the now 4 supported boards)
• broke up existing bnn end2end tests into a per-board option
• refactored existing Jenkins setup to a declarative Jenkins pipeline
• XML results captured for tests - for jenkins GUI
• HTML results captured for docker & hardware tests
• HTML code coverage results captured for test suites: util, streamline, transform, brevitas_export, notebooks, fpgadataflow

When testing on HW, various issues were seen:

• the following commit was needed as U250 tests were failing: https://github.com/Xilinx/finn/commit/e76f20d1d8d05f2d8ddb52ade0f991915672622b
• there were some erroneous results due to incorrect data generated for the HW tests. A workaround was put in just to get some tests passing - so a temporary hack script is seen in this PR. I removed this script when I correctly adjusted the test data here: https://github.com/Xilinx/finn/pull/862/commits/61cba651c155c258fe5a529a2be5d2b3fdf2d3d0 and https://github.com/Xilinx/finn/pull/862/commits/10d34b5fea8904f949c4ddab98cd5c0a1321fa10
• The Jenkinsfile became too large at one point so testing had to be done with multiple job runs. I put the end2end testing and html report code on separate 'feature' branches until I could shrink the Jenkinsfile appropriately and retest

[smtalds]

@fionnodonohoe-xlnx @auphelia Hello, can I get information about Kria KV260? Can we use this board for FINN? Do we submit this information to the FINN documentation if it is available?

[auphelia]

Thanks @fionnodonohoe-xlnx and @johnnoel-xlnx !