baton-github: reorder fields

[Bencheng21]

today.

these two fields should be on the bottom

Summary by CodeRabbit

• Chores
  • Internal configuration structure reorganization with no impact to user-facing functionality.

[coderabbitai]

Walkthrough

Configuration field ordering was adjusted in the Config initialization method: syncSecrets and omitArchivedRepositories were repositioned from after instanceUrlField to after orgField. No functional logic, validation, or exported signatures were modified.

Changes

Cohort / File(s)	Summary
Configuration Field Reordering pkg/config/config.go	Reordered configuration fields in NewConfiguration: moved syncSecrets and omitArchivedRepositories to follow orgField instead of instanceUrlField. No semantic changes or field additions/removals.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 The fields hop and skip in a brand new line,
Rearranged with care, a config design,
No logic bent, no function torn,
Just a tidy dance—configuration reborn! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'baton-github: reorder fields' accurately and concisely describes the main change: reordering configuration fields in the GitHub connector.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch ben/reorganize

---

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

[gontzess]

Does anything in C1 save these in database and expect them in a different order? Don't know enough about how C1 handles the ordering, but just want to make sure this isn't a breaking change

[Bencheng21]

Does anything in C1 save these in database and expect them in a different order? Don't know enough about how C1 handles the ordering, but just want to make sure this isn't a breaking change

I think c1 save these in database, but I don't think the order matters in c1.