test(FTQ): verify BPU response to FTQ and FTQ commit to BPU

[Knight-of-Thunder]

Description

This PR completes testing for two stages of the FTQ-BPU interaction. After the BPU generates prediction results, it sends them to the FTQ. The FTQ then performs a series of operations and ultimately issues a commit back to the BPU, containing information that helps the BPU update its state.

For the first stage, i.e., BPU sending prediction results, the main testing challenge—and the focus of the test cases I wrote—is to ensure that the prediction results are correctly written into the different FTQ sub-queues and status queues.

For the second stage, i.e., FTQ sending commit information back to the BPU, the testing challenge—and the focus of the corresponding test cases—is to verify the conditions under which FTQ can send commit messages to the BPU, as well as the complex logic involved in updating FTB entries.

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

make test target=ut_frontend/ftq/ftq_top/test/test_ftq_top2.py

• Test A: BPU sending prediction results, corresponding to the verification task 1, 2(https://open-verify.cc/verifytask/03_ftq/)

make test target=ut_frontend/ftq/ftq_top/test/test_ftq_top10.py

• Test B: FTQ sending commit information back to the BPU, corresponding to the verification task 10

Test Configuration:

• Firmware version:
• Hardware:
• Toolchain:
• SDK:

Checklist:

• My code follows the style guidelines of this project
• I have added the appropriate labels
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules