Issue Markers are potentially shown in incorrect version

Currently, file markers are reloaded every time the end-version selector in the issue-list is changed. This is not the expected behavior. The markers should rather always be taken from the latest available analysis version and consequently don't need to be reloaded upon end-version change in the issue-list.

See excerpt from the specification document below. This should likely be implemented before the source-code diffing feature that moves the markers to the correct place if the local file differs from the analyzed file.

Editor annotations pipeline: 

1. convert local path to analysis path (server-side path, see path mapping below) 
2. DashboardInfoDto::projects ProjectReferenceDto::url (+ filename argument) → FileViewDto
3. FileViewDto::sourceCodeUrl → plain text source code at analysis time (for diff to correct annotation position, see below)
4. FileViewDto::lineMarkers LineMarkerDto::issueUrl + "/properties" (+ FileViewDto::version as version get argument) → html+css+javascript for issue details, including description