fix: resolve merge conflict in TableClientConfig

[impoiler]

Summary

Resolves a merge conflict in framework/configstore/tables/clientconfig.go that left both HEAD and the incoming branch's version of TableClientConfig in the file simultaneously.

Changes

• Removed the duplicate TableClientConfig struct definition introduced by a failed merge, retaining the correct version with proper field types (e.g., *bool for EnableLogging, typed foreign key references) and full field alignment

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

go build ./...
go test ./...

Breaking changes

• Yes
• No

Related issues

Related to #5251

Security considerations

None. This is a conflict resolution with no behavioral changes.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: 00a042df-b03e-492d-9f8e-ed8664305050

📥 Commits

Reviewing files that changed from the base of the PR and between 8e3443c and a286066.

📒 Files selected for processing (1)

• framework/configstore/tables/clientconfig.go

💤 Files with no reviewable changes (1)

• framework/configstore/tables/clientconfig.go

---

📝 Walkthrough

Summary by CodeRabbit

• Bug Fixes
  • Resolved an issue that could prevent client configuration data from being processed correctly.
  • Preserved existing webhook and global configuration handling.

Walkthrough

Removed leftover merge-conflict markers from TableClientConfig, leaving its existing fields and configuration hooks intact.

Changes

Client configuration cleanup

Layer / File(s)	Summary
Clean TableClientConfig definition framework/configstore/tables/clientconfig.go	Removed conflict-marker artifacts around the struct declaration and field list without changing the surrounding configuration or GORM hook logic.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is concise and accurately summarizes the merge-conflict resolution in TableClientConfig.
Description check	✅ Passed	The PR description matches the template well and includes the required summary, changes, testing, impact, and checklist sections.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 07-18-fix_build

⚔️ Resolve merge conflicts

• Resolve merge conflict in branch 07-18-fix_build

---

_{Comment @coderabbitai help to get the list of available commands.}

[impoiler]

• fix: resolve merge conflict in TableClientConfig #5349 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.
• Every field in the deleted duplicate remains in the retained struct.
• The retained struct also preserves DualCredentialConflictBehavior.

Important Files Changed

Filename	Overview
framework/configstore/tables/clientconfig.go	Removes merge-conflict artifacts and a duplicate field block without changing the effective configuration schema.

_{Reviews (1): Last reviewed commit: "fix: build" | Re-trigger Greptile}