STM32: Fix data alignment issue in HASH function for F2, F7, L4

[bcostm]

Description

This PR fixes an issue with data alignment in ST HAL hash write data function.

This is the same change has the one done in PR #7176 and it fixes Issue #7188.

@KariHaapalehto can you please review it and tell me which test(s) did you use to verify it on the STM32F4 ?

cc @ARMmbed/team-st-mcd for review also

Pull request type

[X] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[KariHaapalehto]

Looks good to me +1.
ARM had a internal issue found in internal testing with mbed cloud client.
I ran internal testcase with GCC_ARM, ARM and IAR compilers with both release and debug profiles to verify fix

[cmonr]

@ARMmbed/team-st-mcd Are y'all alright with the changes?

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 2387
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7205/

Triggering tests

/morph test
/morph uvisor-test
/morph export-build
/morph mbed2-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2022
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7205/

[mbed-ci]

Test : SUCCESS

Build number : 2175
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7205/2175

[cmonr]

Holding to wait for feedback from @ARMmbed/team-st-mcd, just in case.
Otherwise, this should be good to go.

[jeromecoutant]

@bcostm is ST team :-)

[bcostm]

I agree with myself :) No seriously, we need to be coherent. This patch has been added for the F4 devices, so there is no reason to not add it for other STM32 devices... Otherwise we need to revert the F4 patch ...