Prevent two bridge contracts to be deployed for a token

Currently, there is no check that when a token bridge is deployed, that no bridge has already been deployed for that token.
We should figure out if either this isn't a problem at all (i.e. no attack vector), or otherwise fix it