fix: incorrect framework component type

[elsapet]

Description

By mistake we were sending the classification reason as the recipe type for framework detections.

Note: clean up work is required on the Cloud for existing data that has "recipe match" set as its component type, but this Bearer fix can be released independently

Checklist

• I've added test coverage that shows my fix or feature works as expected.
• I've updated or added documentation if required.
• I've included usage information in the description if CLI behavior was updated or added.
• PR title follows Conventional Commits format