"the specific api does not exist" shown if API is selected in `api-details` widget

[Marvin Rensing]

Bug description

The developer portal widget api-details shows "the specific api does not exist" if you initially select an API in the api-list (Dropdown) widget. Even though a valid API has been selected and the API exists.

If you refresh the page after selecting the API, the api-details shows the correct information.

Reproduction steps

1. In the developer portal management ui create a new page containing the api-list (Dropdown) widget and a api-details widget.
   
2. Save and publish
3. Open the just created page in the developer portal as a "normal" user (not the management ui)
4. In API Details component there is a text "The specified API does not exist." even though no API was selected.
5. Select an API in the dropdown
6. the api-details shows the message "the specific api does not exist" instead of the actual API details.
   
7. if you refresh the browser window the API details are shown correctly
   

Once the browser window has been refreshed the dropdown works as expected and changes the api-details content upon change.

Expected behavior

• Before selecting an API from the list, different information than "The specified API does not exist." is displayed because in current approach it is kind of misleading that specified API does not exist even though no API is selected.
• Title in API Details component is populated right away, without refresh required after selecting an API.

Is your portal managed or self-hosted?

Managed

Environment

• Operating system: MacOS
• Browser: Firefox
• Version: 122.0.1

Additional context

none

[Marvin Rensing]

This problem also happens if we use a api-list widget instead of the api-list (Dropdown) widget.

[Marvin Rensing]

When is the fix going to be rolled out?