Fix aws-login unexpected keyword argument error

[zdc217]

Closes #257

[ddriddle]

commit 7e6d3cf contains the actual fix. Everything else is test code or changes to make the code unit testable:

commit 7e6d3cf98587fa09f45cff8f4861afaa270d1a04 (HEAD -> fix/257, upstream/fix/257)
Author: Zach Carrington <zdc@illinois.edu>
Date:   Thu Nov 20 16:02:04 2025 -0600

    Fix aws-login unexpected keyword argument error
    
    Closes #257

diff --git a/src/awscli_login/credentials.py b/src/awscli_login/credentials.py
index 39ef7cd..420ce8a 100644
--- a/src/awscli_login/credentials.py
+++ b/src/awscli_login/credentials.py
@@ -11,7 +11,7 @@ from datetime import datetime
 
 from botocore.session import Session
 
-from .__main__ import main as login, logout
+from .__main__ import main as aws_login, login, logout
 from ._version import version
 from .account_names import edit_account_names
 from .config import Profile, error_handler
@@ -121,7 +121,7 @@ def main():
         if ns.debug_info:
             debug_info()
             return
-        return login(ns, session)
+        return aws_login(ns, session)
     elif args.logout:
         return logout(Namespace(**json.load(args.logout)), session)
     elif args.alias:

[ddriddle]

I am able to reproduce the error without the fix above:

(venv) $ pip install .
(venv) $ aws login --duration 900
(venv) $ date
Fri Nov 21 14:24:05 CST 2025
(venv) $  aws s3 ls

Error when retrieving credentials from custom-process: main() got an unexpected keyword argument 'interactive'

(venv) $ aws-login 
main() got an unexpected keyword argument 'interactive'
$ date
Fri Nov 21 15:47:38 CST 2025

After applying the fix the error goes away:

(venv) $ aws login --duration 900
(venv) $ date
Fri Nov 21 15:50:31 CST 2025
(venv) $ aws s3 ls
(venv) $ date
Fri Nov 21 16:58:22 CST 2025
(venv) $ aws-login
{"AccessKeyId": "FAKE_ID", "SecretAccessKey": "FAKE_SECRET", "SessionToken": 
"FAKE_TOKEN", "Expiration": "2025-11-21T23:57:46+00:00", "Version": 1}

[edthedev]

The test failures here are due to #261, and should clear up after we resolve that.

(Adding blocked label while we work #261.)