Implement Error States and Settings Link for GitHub Integration Panel

[toyamarinyon]

The current GitHub Integration panel in the Agentic-workflow builder app only displays the UI for a successfully authenticated and configured state. This issue tracks the work required to handle other possible states and improve the user experience.

Tasks:

• Implement UI for unauthorized state: When the user has not authorized the application to access their GitHub account, display an appropriate message and a clear call to action to authorize.
• Implement UI for invalid-credential state: When the user's GitHub credentials are invalid (e.g., token expired, revoked), display an error message and guide the user to re-authenticate or update their credentials.
• Add a "Change Settings" link: Provide a clear and easily accessible link within the GitHub Integration panel that allows users to modify their GitHub settings (e.g., re-authenticate, change repositories).
  Context:

Currently, users encountering unauthorized or invalid-credential states may be confused or unable to resolve the issue. Providing clear UI and guidance will improve the user experience and reduce support requests.

Reference:

The following code snippet from another project may be helpful as a reference for implementing these states:

giselle/apps/studio.giselles.ai/packages/components/navigation-panel.tsx

Lines 571 to 593 in 2017cce

	function GitHubIntegration() {
	const { status } = useGitHubIntegration();
	const content = () => {
	switch (status) {
	case "unauthorized":
	return <RequireGitHubAuthorization />;
	case "invalid-credential":
	return <RequireGitHubReAuthorization />;
	case "installed":
	case "not-installed":
	return <GitHubIntegrationForm />;
	default:
	throw new Error(status satisfies never);
	}
	};
	return (
	<ContentPanel>
	<ContentPanelHeader>GitHub Integration</ContentPanelHeader>
	{content()}
	</ContentPanel>
	);
	}

[prakha]

look like a nice issue to work on, can i work on this issue??

[toyamarinyon]

@prakha Thanks for your interest, Prakha! Yes, absolutely, please feel free to work on this issue. We appreciate your contribution!