This is a known bug in SSDT, and we have a work item to fix this. Unfortunately, the only workaround I can offer is to remove STRING_SPLIT from the stored procedure definition and then change the stored procedure definition as an action after the script is deployed.
source
share