Logic issue with linking storages to captures

[Nefarious46]

Description
While writing apidoc an issue was discovered with linking flow storages to captures where wrong ID was used when linking flow storages to captures. This allows linking multiples of the same flow storage BUT with different FLOW.

Should be refactored to only allow linking captures to flow storage with the same FLOW. This should also return error to end user.

[Nefarious46]

Manual testing

one storage with ID = 1

two flows "a" and "b"

two different sinks for 2 different captures with flows "a" and "b"

two captures with ID of 1 and 2

Captures. Same everything but different flow_id
1,1,1,1,1,1,1,relp,1,1,1
2,1,1,1,1,1,1,relp,2,1,2

Flow_targets. Different flow_id but same storage_id
1,1,1,cfe_04
2,2,1,cfe_04

capture_storages. capture_id, flow_id and flow_target_id.
1,1,1,1
2,2,2,1

Conclusion = No constraint errors. Just misleading column name. Change column name to storage_id.

[Nefarious46]

Awaits changes from cfe_31 that properly link storages per capture.