Log why a new repository couldn't be created - #436

When a repository isn't in Socket yet and the API token can't create it (for example, the token has repo:list but not repo:create), the CLI exits 2 right after file discovery with nothing logged, so CI users have no way to tell what went wrong. Related to CE-127.

Root Cause

get_repo_info sets the socketdev logger to CRITICAL around the repository lookup and only restored the level after a successful lookup. socketsecurity.core logs through that same logger, so when the lookup raised (a 404 for a repository Socket hasn't seen), the "attempting to create it" warning and the creation error were both dropped before sys.exit(2). When the create succeeded, logging stayed muted for the rest of the run.

Fix

• Restore the logger level in a finally around the lookup.
• Include the repository, the HTTP status and, on a 403, a repo:create hint in the creation error. The SDK keeps only the API's Insufficient permissions message and drops the required scope from the response.
• The exit code on this path is unchanged (2).
• Two tests in tests/core/test_sdk_methods.py. Both fail on main: no records reach the log, and the logger is still at CRITICAL after a successful create.

Testing

• uv run pytest tests/unit tests/core: 729 passed. ruff check clean, uv lock --locked in sync, hatch build + twine check pass.
• Live against the API with a token that has repo:list but not repo:create, on a repository Socket hadn't seen:
  • Before (2.5.0 and 2.11.6): exit 2, the log ends at File count (1) is within file descriptor limit.
  • After, at the default log level: exit 2 with

    Failed to get repository <repo>, attempting to create it
    API failure while creating repository <repo> (HTTP 403): Insufficient permissions
    A 403 here usually means the API token is missing the repo:create scope.
    

• Same token after adding repo:create: the CLI creates the repository and completes the scan (exit 0), with logging continuing after the create. A rerun on the now-existing repository takes the normal path with no create attempt.

Public Changelog

The Socket Python CLI now explains why it couldn't create a repository that isn't in Socket yet, including the HTTP status and a hint about the repo:create scope, instead of exiting with no output.