Fix bad transport being used for 2nd pairing attempt

After accepting the PIN, we would store device type that we received in
remote features. If pairing is canceled, and triggered again, this
information should be forgotten - otherwise it could impact transport
selection logic for subsequent pairing.

Bug: 344574871
Bug: 343119130
Flag: bond_transport_after_bond_cancel_fix
Test: Attempt to bond 2 phones. Accept PIN on initiator, but cancel
      bonding on Acceptor. Then, re-initiate pairig again.
Test: mma -j68
Change-Id: Ibc8ae4f33c8ee461ecaa6b39666bbd1e1967c7e0