Current implementation of resource queue can not guaranty the strong
consistency of configuration of resource limit between catalog and
shared memory, so AssertMemoryLimitsMatch() is incorrect and
unreasonable. We may need to guaranty the consistency some day, but for
now just remove the obvious wrong assertion.

and 42cab821, since new PANIC
issues are found related to them.

failure fixed)

In some error cases, the resource queue lock is not released, hence
leading to lock leak and inconsistent resource queue status; this commit
overhauls the resource queue locking code to complete the cleanups if error
or signal happens during acquiring resource queue lock; meanwhile, some
unnecessary code blocks are removed and unreasonable code are fixed to make
it easier for reading and understanding;

This reverts commit b46f781f.

In some error cases, the resource queue lock is not released, hence
leading to lock leak and inconsistent resource queue status; this commit
overhauls the resource queue locking code to complete the cleanups if error
or signal happens during acquiring resource queue lock; meanwhile, some
unnecessary code blocks are removed and unreasonable code are fixed to make
it easier for reading and understanding;