Update unicode-width

[extrawurst]

No description provided.

[micl2e2]

Thanks for the reminder!

It seems like the recent updates of unicode-width have introduced some compatibility issues to downstreams like us. Several tests in this crate would fail even with a minor version change (to 0.13.0). By indicating ^0.1.0 in our cargo file, we already assumed that we'd be totally fine with any possible updates as long as they follow the semver convention so that our crate remains consistent. Unfortunately, the major version for the latest one 0.2.0 is still unchanged, which means it is uncertain whether there would be similar changes being introduced in its future updates.

But something for bwrap is already certain: if any breaking changes are introduced, our crate's major version will move forward, that say, the next update will be either locking unicode-width's version to the original one, or bumping the major version to 2. I am still trying to figure out the actual benefits that we could gain from unicode-width's recent updates, and will take action after evaluating the tradeoff.

[extrawurst]

@micl2e2 how do you want to move forward with this?

[micl2e2]

The current code has been working fine since their previous fix (unicode-rs/unicode-width#67). The changes in 0.2 fails more half of our tests, would require significant changes to the algorithm. Currently I just don't have time for any extra new feature implementing for this crate so, unless all tests being passed, the unicode-width might stay 0.1.x for a while