Persist authenticator items to a database

[KatherineInCode]

📔 Objective

This moves to AuthenticatorItem as the primary thing owned by the application—analogous to Cipher in the main app—and builds the persistence layer for creating/updating/deleting items from the internal store. Create and update are wired up to the views; delete will come in another PR because it requires moving around some UI things. An edit does not currently update the View Item screen; this will be fixed when the flow gets updated to match the current intended UI. A number of references to Token are still scattered in the code and comments, most of which should get zapped with the UI update coming soon-ish.

📸 Screenshots

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – f25d3d2a-965a-4438-b387-2d55e7775ecb

No New Or Fixed Issues Found