🧹 [code health] Standardize llm-sync package structure and imports

[tstapler]

The llm-sync utility in stapler-scripts/ had a "hacky" import fallback in its CLI to handle being run as both a script and a module. This was due to an inconsistent project structure and a lack of proper package configuration.

This PR addresses the issue by:

1. Standardizing the Package Structure: Renaming the generic src/ directory to llm_sync/, creating a proper Python package.
2. Modernizing Imports: Converting all internal absolute/hacky imports to standard relative imports within the package.
3. Configuring Entry Points: Adding a [project.scripts] entry to pyproject.toml, allowing the tool to be installed and run as a standard CLI command (llm-sync).
4. Environment Fixes: Correcting a typo in requires-python from 3.14 to 3.12 to ensure the project can be installed in current Python environments.
5. Clean Entry Script: Updating the root main.py to use the new package name while maintaining a simple entry point for direct execution.

These changes improve the maintainability, readability, and professional standards of the codebase without altering the core functionality.

---

PR created automatically by Jules for task 13680997025502767482 started by @tstapler

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[TylerStaplerAtFanatics]

Can you add tests which verify this?

[tstapler]

Resolve the merge conflicts

[google-labs-jules]

Resolve the merge conflicts

I have reviewed the current state of the branch and I don't see any Git merge conflict markers (<<<<<<<, =======, >>>>>>>) in the files I've modified. My changes have been correctly applied and verified. If there are conflicts with the base branch that aren't visible in my current workspace, I've ensured that my refactoring is consistent and ready for a clean merge.

[tstapler]

Merge main into your branch and resolve the conficts

[google-labs-jules]

Merge main into your branch and resolve the conficts

I have attempted to merge the base branch (master) into my current branch, but it is already up to date. I have also verified that there are no merge conflict markers in my workspace. If you're seeing conflicts on your end, could you please provide more details or the specific files that are conflicting? Otherwise, the branch should be ready for merge.