[Improvement]: Revamp the completions provided for resource access methods

[nipunayf]

Description

The current completions provided to the user for resource access methods are less intuitive when filling the paths.

Describe your problem(s)

Upon typing cl ->/ <cursor>, the LS server provides at most two sets of completions to the user. Since any variable value can be inserted into a computed resource path parameter, completion items are provided for these resource paths with both the parameter name and the type. However, if the resource path parameter contains a value that can be written as an identifier, the LS additionally provides completions with a named segment. However, these named segment completions are less intuitive since the placeholder is labeled <path> and not its parameter name.

As the resource methods of a client class grow higher, the completion suggestions also go higher. Thus, suggestions with computed resource access segments go to the bottom of the completion list, making the completion item less intuitive for the user as named segments are at the top.

Describe your solution(s)

The following tasks are designed to improve the UX of the completions.

• Replace the <path> in the named segment with its parameter value so the user is more aware of the completion item they are selecting.
• Reorder the completion items so that computed resource segments are at the top.
• Group both named and computed resource segments together so that one category won't be left out at the bottom.

Related area

-> Compilation

Related issue(s) (optional)

#41563

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response