fix(console): refresh UI after API detach from automation source

[ankita-gupta21]

Issue

https://gravitee.atlassian.net/browse/APIM-13877

Description

Reload General Info via refresh$ instead of re-running ngOnInit, refresh lastApiFetch after detach, and update danger zone detach/read-only state when originContext changes.

Additional context

api-general-info: Replace (reloadDetails)="ngOnInit()" with reloadDetails() that triggers the existing refresh$ subject, so the API is refetched without stacking duplicate subscriptions.
ApiV2Service.detach(): Chain refreshLastApiFetch() after _detach (same pattern as deploy) so getLastApiFetch() consumers (e.g. API navigation) receive the updated originContext.
api-general-info-danger-zone: Move canDetach / isReadOnly into updateOriginContextState() and call it from ngOnChanges when the [api] input changes, so the Detach action hides after reload.

Screen.Recording.2026-05-30.at.11.21.04.AM.mov

[gemini-code-assist]

Code Review

This pull request refactors the API general info danger zone component by extracting origin context state updates into a reusable method and triggering it on changes. It also updates the API service's detach method to refresh the last API fetch automatically. Feedback on these changes includes adding optional chaining to prevent potential runtime errors when the API input is null, removing a redundant method call in ngOnInit since ngOnChanges runs first, and mapping the detach observable stream to undefined to avoid strict TypeScript type mismatches.