`check.canSetManagementProxy` incorrectly thinks that the current proxy cannot assign a new proxy

[resonant-riches]

https://github.com/urbit/azimuth-js/blob/aa52d2a70e53661ce02d0d9fefac7cf7b3d193f2/check.js#L206C22-L208

In fact, the address which is currently the management proxy is also able to call setManagementProxy. Here is an example of such a transaction https://etherscan.io/tx/0xa377e129ec21402dffc3de3bfee5554474494c17e0ea02b1bdf76e0d497114ae

[resonant-riches]

I haven't tried this with the spawn and voting proxies, but I would not be surprised if the same applies there.

[resonant-riches]

I think just using isActivePointManager instead of isActivePointOwner is enough, but I might be wrong there.