stagingapi: update_status_comments() include link to dashboard.

[jberry-suse]

Requested in #573.

Fully tested by running:

api.update_status_comments('openSUSE:Leap:42.3:Staging:adi:9', 'select')

Which resulted in the correct link in comment.

I debated if the link should be placed around a new piece of text like (dashboard) or somesuch, but given the comment is on the project page the only other relevant link related to just the project seems like dashboard. Either way easy to change since url is correct.

The new extract_staging_short() from request_splitter did the trick and works for both letter and adi. :)

[coveralls]

Coverage increased (+0.1%) to 45.489% when pulling 55c4382 on jberry-suse:update_status_comments-dashboard into 6eefb42 on openSUSE:master.

[jberry-suse]

Could potentially drop the apiurl and use a path relative to root (this assumes the server referenced by apiurl is not hosted in subdir (which I am not sure if OBS even supports)). The url would just be /project/staging_projects/... instead of http://..../project/staging_projects/....

[lnussel]

the adi seems gone again. apiurl would be api.o.o, right? We need build.o.o

[jberry-suse]

I remember reading the code in obs_factory, and in practice it seems to work since the plugin redirect internally for paths that are part of the application and not API. I can change it, but then I imagine it either needs to be hardcoded or derived from the apiurl which is potentially b.o.c specific. Long-story short api.o.c works.

Alternatively the relative path describe in my previous comment.

[jberry-suse]

For example: https://api.opensuse.org/project/staging_projects/openSUSE:Leap:42.3/A works just fine.

[jberry-suse]

I just confirmed the relative approach works as well so perhaps just use that?

[text](/project/staging_projects/openSUSE:Leap:42.3/A)

[lnussel]

ah, the api link works if logged in. I don't mind either way.