feat: completion list suggests constructor like & builder methods first

[mustakimali]

When typing MyType:: the completion items' order could be re-ordered based on how likely we want to select those:

• Constructors: new like functions to be able to create the type,
• Constructors that take args: Any other function that creates Self,
• Builder Methods: any builder methods available,
• Regular methods & associated functions (no change there)

In this photo, the order is:

• new constructor is first
• new_builder second is a builder method
• aaaanew is a constructor that takes arguments, is third and is irrespective of its alphabetical order among names.

---

Another Example using actix HttpServer shows preferring constructor without self arg first (the new method)

I've dropped my previous idea of highlighting these functions in the rustdoc (rust-lang/rust#107926)

[bors]

☔ The latest upstream changes (presumably #16274) made this pull request unmergeable. Please resolve the merge conflicts.

[rustbot]

There are merge commits (commits with multiple parents) in your changes. We have a no merge policy so these commits will need to be removed for this pull request to be merged.

You can start a rebase with the following commands:

$ # rebase
$ git rebase -i master
$ # delete any merge commits in the editor that appears
$ git push --force-with-lease

The following commits are merge commits:

• 5d35e44

[Veykril]

Thanks!
@bors r+

[bors]

📌 Commit 2c76104 has been approved by Veykril

It is now in the queue for this repository.

[bors]

⌛ Testing commit 2c76104 with merge 3c4d642...

[bors]

☀️ Test successful - checks-actions
Approved by: Veykril
Pushing 3c4d642 to master...