Remove workflows from GET profile endpoint + Add inUse flag

[tw4l]

Connected to #2661

• Removes crawl workflows from being returned as part of the profile response.
• Frontend: removes display of workflows in profile details.
• Adds 'inUse' flag to all profile responses to indicate profile is in use by at least one workflow
• Adds 'profileid' as possible filter for workflows search in preparation for filtering by profile id ([Change]: Additional workflow filtering options: profiles, lastCrawlState #2708)
• Make 'profile_in_use' a proper error (returning 400) on profile delete.

[ikreymer]

Added inUse flag to the profile object to indicate that a profile is in use and can't be deleted, without having to enumerate all workflows.

Do we actually want to list workflows on the profile detail, rather than add a new filter (following the refactoring in #2702) in the workflow section?

[tw4l]

Added inUse flag to the profile object to indicate that a profile is in use and can't be deleted, without having to enumerate all workflows.

I think we need to add this back to the list component delete as well (edit: done).

Do we actually want to list workflows on the profile detail, rather than add a new filter (following the refactoring in #2702) in the workflow section?

I think it's useful to be able to go to the workflow quickly from the profile - my take would be that we do both (edit: from Discord, solution is likely to add a link to the filtered workflow list from the profile detail)

[tw4l]

Deletion notifications are now fixed:

Following #2702 , we discussed adding a workflow filter by profile and linking to that from the profile detail rather than creating yet another paginated workflow component.

[ikreymer]

Deletion notifications are now fixed:

Great! One we have filtering by profiles (eg. #2708), the error could include a link to workflows with that profile. Otherwise, I think this is good for this issue!