[release plan] Release status data on the dashboard is sometimes wrong

Problematic release plan: https://azsdk-releaseplan-dashboard-hveph5aqhhcfhtgu.westus-01.azurewebsites.net/?releaseplan=35307

The JS SDK PR which targets a different version is still open, but the release status is 'Released'. And the version 7.0.1 was released a month ago, not related to this plan. The release status, version, and package link should not be set.

We encountered this issue several times:
[Release plan data inconsistent for Commvault.ContentStore](https://teams.microsoft.com/l/message/19:084875bb626242ed95f3ac8dddfaa12a@thread.skype/1787131858323?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&parentMessageId=1787131858323&teamName=Azure%20SDK&channelName=SDK%20release%20support&createdTime=1787131858323)
[Release plan for EventHub - status mismatch](https://teams.microsoft.com/l/message/19:084875bb626242ed95f3ac8dddfaa12a@thread.skype/1785728387375?tenantId=72f988bf-86f1-41af-91ab-2d7cd011db47&groupId=3e17dcb0-4257-4a30-b843-77f47f1d4121&parentMessageId=1785728387375&teamName=Azure%20SDK&channelName=SDK%20release%20support&createdTime=1785728387375)

Start with the linked release-plan dashboard and reproduce release plan 35307, comparing its displayed status, version, and package link with the open JS SDK PR and the actual 7.0.1 release. Trace the dashboard's release-plan data source and matching entry point, then check the Commvault.ContentStore and EventHub examples. Done means unrelated releases no longer populate these fields.

Written by the indexing model from the issue text.