MAINT: IPython history file per host + configurable

[ZLLentz]

Description

Main changes:

• Add a --hist-file cli argument
• Default the history file to /u1/${USER}/hutch-python/history.sqlite (local disk)
  • Previously: normal IPython history per user home directory on NFS
• Add a unit test

Minor changes:

• Make the cli args type-hinted
• Fix some minor styling inconsistencies

Motivation and Context

https://jira.slac.stanford.edu/browse/ECS-5096

• On NFS for some of our endstations, there are some file locking issues related to the ipython history file.
• Bringing it off of NFS should theoretically alleviate the issues, at the cost of fracturing history per-host.
• Use CLI over cfg file because this would hypothetically need to be configured per-session, whereas the cfg file is shared between all sessions for one hutch.

How Has This Been Tested?

• Interactively as me
• Unit tests
• Tested as xcsopr and it works as expected: each of xcs-daq and xcs-control has its own separate history file

Where Has This Been Documented?

Only here, I need to write pre-release docs

Pre-merge checklist

• [x] Code works interactively (a real hutch config file can be loaded)
• [x] Code contains descriptive docstrings, including context and API
• [x] New/changed functions and methods are covered in the test suite where possible
• [x] Test suite passes locally
• [x] Test suite passes on GitHub Actions
• [x] Ran docs/pre-release-notes.sh and created a pre-release documentation page
• [x] Pre-release docs include context, functional descriptions, and contributors as appropriate

[ZLLentz]

If I understand this right, the way to return to the previous behavior

You've made me realize that the opr actually has no simple way to return the old previous behavior, as written. The only supported solution is to not make the special folder.

:memory: is actually an ipython built-in magic value for not using a file at all and storing the session history in the process memory.

[ZLLentz]

dataclass-namespace-for-cli-args thing too

I'm a fan of this because it helps vscode keep track of which arg is supposed to be which type

[ZLLentz]

tbh it just makes it so I can add $HOSTNAME to the default later if we decide to do something like that