Handle hadolint check failure with proper risk assessment

[pullurib]

PR description

Suppressing/Ignoring hadolint warning about the last USER in Dockerfile being the root user - with reasoning that the root user has very specific job to do and then besu runs as besu user .

Follow up to #7575

Fixed Issue(s)

Follow up fix to #4292

[fab-10]

Still something not working https://github.com/hyperledger/besu/actions/runs/10927512262/job/30333865457 seems related to testDocker task

[pullurib]

Looking into it, that gradle task runs fine locally on my Mac

[fab-10]

Running it on Linux we get this report

<testcase name="File /var/lib/besu owner" time="0.000">
<system-err>File: /var/lib/besu: owner: Expected &#34;root&#34; to equal &#34;besu&#34;</system-err>
<failure>File: /var/lib/besu: owner: Expected &#34;root&#34; to equal &#34;besu&#34;</failure>
</testcase>

the expected user does not match

[fab-10]

Fix for the CI issue #7655

[pullurib]

@fab-10 Thanks for taking care of it. I wasn't able to repro with act runs and was planning on uploading the reports to see what was failing. This is a better approach to wait for besu that waiting a few seconds .