Deploy dacpac fails with compatibility set to 130
I had (have) this same problem.

When the dacpac generates the script, it queries the target database to see what objects are there. One or more of those queries went from sub second to much longer, when we moved to 2016. By updating the statistics of some system tables I was able to bring it back down to normal behavior. 

update statistics sys.sysschobjs;
update statistics sys.sysobjvalues;
update statistics sys.sysidxstats;
update statistics sys.syssingleobjrefs;


So, I don’t know exactly what changed to make SQL Server run those queries slowly, but this is how we've solved the problem.