standardize import parameters schema

[parkedwards]

we have a couple of fragmentations

• some take both name / ID, but prefix name with name/<name>
• some only take ID

some of this is due to the resource API itself, because we may not be able to query by both. but in cases that we can, we should standardize the name import with the name/ prefix

however, we should also be standardizing the workspace_id structure. for example:

• some resources expect workspace_id,resource_id (webhooks, work pools, flow)
• some resources expect resource_id,workspace_id(blocks, automations, variables)

we should definitely standardize that