Change the uprev branch, MR, and issue name patterns

Two issues are related to this merge request: #14 (closed) and #25 (closed)

The titles for the merge requests created by ci-uprev distinguish between when it can work directly or when it needs to update the expectation files. The difference between them will be a "draft" prefix when the proposal comes with changes in the expectations.

Having two merge requests can help the integrator to decide what would be merged. But the titles, as they are, require the integrator to play with both in case the preference is with the one with an expectations update.

With this change, the integrator can work on one without affecting the other. Then, the integrator will proceed with the more relevant one.

The branch titles were first writing the dependency name, then mentioning it is an uprev (e.g. mesa-uprev or piglit-uprev). The list of branches in a fork can hold other working proposals, and with this change, all the uprev branches will be listed together and subsorted by dependency (e.g. uprev-mesa or uprev-piglit).

Also, the branch that works with an uprev that requires an expectations update was tagged as wip when it doesn't have this sense, especially when it was removed the "draft" from the title.

Bot changes together to avoid collision issues with existing uprev merge requests.

Finally, a fail-safe has been included in this merge request. It is a commit search protection while creating the uprev merge request. This will prevent the job from failing when the gitlab infrastructure requires a bit of time to show the uprev commit in the principal project as part of the merge request.