Fix flash M25P16 ID with QUADSPI

[mluessi]

Fixes the M25P16 flash identification when used with QUADSPI

[github-actions]

Do you want to test this code? Here you have an automated build:
Assets
WARNING: It may be unstable. Use only for testing! See: https://www.youtube.com/watch?v=I1uN9CN30gw for instructions for unified targets!

[blckmn]

AUTOMERGE: (FAIL)

• github identifies PR as mergeable -> FAIL
• assigned to a milestone -> PASS
• cooling off period lapsed -> PASS
• commit count less or equal to three -> PASS
• Don't merge label NOT found -> PASS
• at least one RN: label found -> PASS
• Tested label found -> FAIL
• assigned to an approver -> FAIL
• approver count at least three -> FAIL

[hydra]

The code in master prior to this commit should have caused a compilation error, but is seems there is no automated build that compiles in both QUADSPI and the M25P16 flash chip.

The issue stemmed from two PR's making changes to the same code, one or the other of the PR's should have had a failing build at the time they were merged. See #11825 and #12103.

@haslinghuis @blckmn This situation can be avoided if there is a pre-merge check that builds all the targets and that at least one target exists for the QUADSPI/M25P16 combination. The development Nucleo board targets used to cover many of the combinations prior to their removal.

Currently the code-base cannot be relied on to even compile.

[haslinghuis]

@blckmn Would like to restore the NUCLEO F446RE target as I ordered this board.

[blckmn]

@haslinghuis lets restore that target, and add it to the checks.