Fix Urdr panic when user has starred a closed issue

[kusalananda]

The issues.json Redmine endpoint does not, by default, return data for closed issues. This means that when a user has starred a Redmine issue that later is closed, Urdr can't find any information about it and panics. The panic is due to accessing the first element from an empty array, which is empty because there was no information from Redmine about the issue, because it was closed.

Related issue(s) and PR(s)

This PR closes #1002.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Other

List of changes made

This PR allows us to find the project ID for closed Redmine issues that a user has starred in Urdr. This is done by adding status_id=* as a query parameter to the relevant REST API call.

Screenshot of the fix

Testing

To test: Star a closed issue (for example 7398) and reload. You will have problem seeing your favourites.

With the PR, this should work.

Further comments

Definition of Done checklist

• I have made an effort making the commit history understandable
• I have performed a self-review of my own code and commented any hard-to-understand areas
• Tests and lint/format validations are passing
• My changes generate no new warnings

[KattisLej]

Great job, now the favourites were loaded although I had a closed issue as a favourite