Modify URI construction logic in ThesaurusService

[f-necas]

When a thesaurus contains keys which can be contained in another, it may display the wrong key when editing a metadata.

By example, there's two thesaurus keys http://domain.com/mykey/1 and http://domain.com/mykey/12.

Depending on the order in the thesaurus, if I have the first one in my metadata record, geonetwork may answer with the second one.

How to replicate:

• Import this thesaurus place-test.zip
• Edit/create a record and add this thesaurus with Test 1 keyword
• Save and close
• Check value: Will be ok Test 1
• Re-edit the record and go to thesaurus part
• 🚫 The value show will be Test wrong

Checklist

• I have read the contribution guidelines
• Pull request provided for main branch, backports managed with label
• Good housekeeping of code, cleaning up comments, tests, and documentation
• Clean commit history broken into understandable chucks, avoiding big commits with hundreds of files, cautious of reformatting and whitespace changes
• Clean commit messages, longer verbose messages are encouraged
• API Changes are identified in commit messages
• Testing provided for features or enhancements using automatic tests
• User documentation provided for new features or enhancements in manual
• Build documentation provided for development instructions in README.md files
• Library management using pom.xml dependency management. Update build documentation with intended library use and library tutorials or documentation