to that end: make `SIMKind` easier to hold by making internals, as well
as the raw CONFIG[:sims] entry, protected

It doesn't do anything we need and causes us to need more config we'd
rather not have

- should behave identically to previous script if no rows found,
  manually running it just produces an empty array for
  `PortRepo::Db.list`, i guess our client knows about no rows errors
- allowed `OptionParser.new` to hold a huge block because this block is
  just naturally very large. Alternatively, we could write separate
  files just for argument parsing, eg `lib/bin_arg_parsers/{args.rb,
  parser.rb}`. But that's probably a separate ticket

problem was that AvailableNumber.for sometimes returned a promise,
sometimes not, causing us to try to call `catch_after` on a Tn

Also redeem the invite at the time if found. HACK: always assumes USD plan

And don't return anything where source starts with xmpp: we'll use that
for internal inventory stuff like offer codes.

* 'downcase-jids' of https://git.secluded.site/sgx-jmp:
  fix: make JID lookups case-insensitive

Centralizes JID normalization in QueryKey::JID.for and ensures Redis
stores lowercase JIDs in create/change_jid methods.

Fixes: https://todo.sr.ht/~singpolyma/soprani.ca/203

- detect if resource-part indicates a client that renders open
  validation in forms

To diagnose ~singpolyma/soprani.ca#493

registered? never returns nil, no need to handle it

Display customer ID and contact information (Jabber ID, phone number)
when selecting actions to help admins identify which customer they're
working with.

Implements: https://todo.sr.ht/~singpolyma/soprani.ca/465
Assisted-by: MiniMax M2 via Crush <crush@charm.land>

We have a loader, let's use it

Probably we want to load list of command as part of the sgx repo? But
maybe that's too heavy and we don't always need it?

* '380-set-port-out-pin' of https://git.secluded.site/sgx-jmp:
  feat: add command to set port-out PIN

Currently, port-out PINs require manual intervention from support. This
command allows customers to self-manage their port-out PINs. Actual
functionality is delegated to the user's backend. For now, that's just
sgx-bwmsgsv2.

References: https://todo.sr.ht/~singpolyma/soprani.ca/380

- uses solargraph sourcemap, which requires a patch for Ruby 3.4
that is not available (patched solargraph version is incompatible
with pinned rubocop)

- conditionally checks for two different kinds of ivar nodes
using the same check that solargraph uses internally to decide between
current and legacy parsers