ResourceManager should avoid allocating AM to same node repeatedly in case of AM launch failures

We have seen that if AM launch fails on some node due to configuration or bad disk issue YARN-3591, quite often it gets reallocated on the same node, causing job failures if the AM attempt limit is reached.

It would be preferable if the scheduler can try to allocate AM on different nodes for subsequent attempts