Chromium bluetooth now distinguishes prepare write from regular write, such that the client is able to know whether a request is a prepare write.

For now, we regard prepare writes as regular writes, which is the existing behavior. However, a better implementation is to queue all the pending prepare writes and apply them when |has_subsequent_request| is false.