rename MPT codes

[shawnxie999]

• tecMPTOKEN_EXISTS renamed to tecDUPLICATE
• tecMPT_MAX_AMOUNT_EXCEEDED renamed to tecPATH_DRY
• tecMPT_LOCKED renamed to tecLOCKED.
• tecMPT_NOT_SUPPORTED is deleted
• tecMPT_ISSUANCE_NOT_FOUND reamed to tecOBJECT_NOT_FOUND

High Level Overview of Change

Context of Change

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Refactor (non-breaking change that only restructures code)
• Performance (increase or change in throughput and/or latency)
• Tests (you added tests for code that already exists, or your new feature included in this PR)
• Documentation update
• Chore (no impact to binary, e.g. .gitignore, formatting, dropping support for older tooling)
• Release

API Impact

• Public API: New feature (new methods and/or new fields)
• Public API: Breaking change (in general, breaking changes should only impact the next api_version)
• libxrpl change (any change that may affect libxrpl or dependents of libxrpl)
• Peer protocol change (must be backward compatible or bump the peer protocol version)