Support for cl_khr_fp16 with embedded profile in test_bruteforce

Current progress of `test_bruteforce` (PR #1681 ) does not take into account difference in processing for embedded profile with `cl_khr_fp16` extension. To keep the scope of changes in #1681 manageable this issue has been introduced.

Start by reading the current progress of `test_bruteforce` in PR #1681 and compare its processing with the embedded profile when `cl_khr_fp16` is present. Done means the test accounts for that extension-specific processing without expanding the original PR's scope.

Written by the indexing model from the issue text.