More explicit Confluence Connector

[pablodanswer]

Description

Relevant docs update: danswer-ai/danswer-docs#114

Update Confluence connector to be more explicit

• Split up 1 url -> wiki url, space name, page ID, and cloud (boolean)
• Explicitly specify cloud vs. datacenter

How Has This Been Tested?

• (With page ID) Create confluence connector on main -> upgrade and ensure indexing still works
• Above but without page ID
• Create confluence connector on this branch -> downgrade to main and ensure indexing still works
• Above but without page ID

Accepted Risk

[Any know risks or failure modes to point out to reviewers]

Related Issue(s)

[If applicable, link to the issue(s) this PR addresses]

Checklist:

• All of the automated tests pass
• All PR comments are addressed and marked resolved
• If there are migrations, they have been rebased to latest main
• If there are new dependencies, they are added to the requirements
• If there are new environment variables, they are added to all of the deployment methods
• If there are new APIs that don't require auth, they are added to PUBLIC_ENDPOINT_SPECS
• Docker images build and basic functionalities work
• Author has done a final read through of the PR right before merge

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
internal-search	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 2, 2024 0:04am

[Weves]

Can we also change the docs for confluence accordingly + link that PR in this PR 🙇

[Weves]

Also, fyi @pablodanswer just updated the Github secrets to work with this PR