interfaces/builtin: Add additional OneSpan devices

[jovasco]

This adds the PIDs of our new devices.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.42%. Comparing base (55d3556) to head (dcf4984).

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #17683      +/-   ##
==========================================
+ Coverage   78.36%   78.42%   +0.05%     
==========================================
  Files        1417     1405      -12     
  Lines      200507   200220     -287     
  Branches     2503     2503              
==========================================
- Hits       157129   157024     -105     
+ Misses      33953    33779     -174     
+ Partials     9425     9417       -8     

Flag	Coverage Δ
unittests	78.42% <ø> (+0.05%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

Mon Sep 21 12:39:36 UTC 2026
The following results are from: https://github.com/canonical/snapd/actions/runs/35595349680

No spread result artifacts found

No spread results JSON artifacts were available for this workflow run, so spread failures (if any) could not be reported.

[bboozzoo]

can you check that the new devices are correctly identified by systemd as security tokens? if you run udevadm info /dev/bus/usb/<bus>/<port> (use lsusb to identify bus & port), there should be ID_SECURITY_TOKEN property listed in the output.

[bboozzoo]

OTOH, looking at my yubikey the property is not listed on the direct usb device, but rather on the hidraw device, so maybe it's best to udevadm info --export-db and then look for ID_SECURITY_TOKEN