[ISSUE #4109] add permission validation on broker side for ordinary topic

[MatrixHB]

to solve the problem described in ISSUE #4109

This change will cause the broker to throw a "NO_PERMISSION" exception. If the producer uses SYNC mode, it will retry sending to another broker, seeing DefaultMQProducerImpl#sendDefaultImpl, so the SYNC mode will not be affected.

[coveralls]

Coverage decreased (-0.2%) to 51.728% when pulling 9e9c160 on MatrixHB:fix_broker_permission into e7c87fa on apache:develop.

[coveralls]

Coverage decreased (-0.2%) to 51.728% when pulling 9e9c160 on MatrixHB:fix_broker_permission into e7c87fa on apache:develop.

[dongeforever]

Adding the perm check for ordinary topic, the client will get exceptions and cannot failover during the matadata discovery time, which is up to 30 seconds.

For ordinary topics, the original design expects the client to discover the new topic route and send only to the writable brokers, which introduces no exceptions and makes the wipe-perm process more smoothly.

[MatrixHB]

Adding the perm check for ordinary topic, the client will get exceptions and cannot failover during the matadata discovery time, which is up to 30 seconds.

For ordinary topics, the original design expects the client to discover the new topic route and send only to the writable brokers, which introduces no exceptions and makes the wipe-perm process more smoothly.

Thanks, this change is not so elegant actually. Maybe updating the client version is enough to solve this problem. Next time we meet this trouble we can discuss this again.