What is the purpose of the change

review #5734

Brief changelog

• Rename constants to represent what it means:
  DEFAULT_LOAD_FACTOR -> DEFAULT_CAPACITY
  DEFAULT_EVICTION_CAPACITY -> DEFAULT_EVICTION_FACTOR
• Refactor codes:

if (map.containsKey(key)) {
         node = map.get(key);
         if (node != null) {
               CacheNode.withdrawNode(node);
         }
         node.value = value;
         freqTable[0].addLastNode(node);
         map.put(key, node);
 }

• Add test case org.apache.dubbo.common.utils.LRUCacheTest#testErrorConstructArguments.

Verifying this change

Run test case org.apache.dubbo.common.utils.LRUCacheTest

Follow this checklist to help us incorporate your contribution quickly and easily:

• Make sure there is a GITHUB_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
• If this contribution is large, please follow the Software Donation Guide.