Duplicated client order IDs can cause orders to be rejected by the exchange and can cause issues with historical analysis of strategy performance. Currently, the client uses a nonce derived from the current timestamp to generate "unique" client order IDs. The issue is that those IDs can be duplicated across multiple instances of hummingbot running in parallel. To prevent this from happening, this PR introduces a new method of generating the IDs that will be unique across instances as well.