The manual attempt could not reproduce any of those errors. Taking further investigation on github actions have been able to figure out the reason why the tests were failing before and made commits (a8cd9eb, a6665d8) that made the tests pass. Though there remains only two tests failing which am investigating but I realize enabling the includes.csrftoken functionality makes all the tests fail login step probably because the functionality was introduced in platform 2.6.0 and the uat is using 2.5.9.
Unable to locate element: *[name='OWASP-CSRFTOKEN']
I may not tell why we are not using the recent released platform version, @jwnasambu could you help me understand the pitfall that were occurring when using the new version which led to this downgrade?