Do not reset max applications for a queue based on absolute capacity

When we use absolute resource configuration in capacityscheduler, the max applications will be reset based on queue‘s absoluteCapacity.

When the cluster is just started and nodemanager has not been registered, max applications will be set to 0, so the application cannot be accepted.

RM log:

LeafQueue:root.hadoop, maxApplications=0, maxApplicationsPerUser=0, Abs Cap:NaN
Queue root.hadoop already has 0 applications, cannot accept submission of application: application_1648803955766_0001

I think  it's meaningless to reset max applications, so we can just delete these codes.