KBS Pin appeared to matched but reg lock still failed

[skipper-83]

Couldn't find an issue for this one unfortunately:

2025-03-03T15:05:42.714+0100 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_RUNTIME_DIR not set, falling back to temp dir
2025-03-03T15:05:42.739+0100 [main] DEBUG org.asamk.signal.App - Starting signal-cli 0.13.13
2025-03-03T15:05:44.429+0100 [main] DEBUG org.asamk.signal.util.IOUtils - XDG_DATA_HOME not set, falling back to home dir
2025-03-03T15:05:44.869+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Starting...
2025-03-03T15:05:45.504+0100 [main] INFO  com.zaxxer.hikari.pool.HikariPool - HikariPool-1 - Added connection org.sqlite.jdbc4.JDBC4Connection@71b3bc45
2025-03-03T15:05:45.505+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Start completed.
2025-03-03T15:05:49.530+0100 [OkHttp https://svr2.signal.org/...] INFO  LibSignal - [Svr2Socket]: [onClosing] code: 1000, reason: 
2025-03-03T15:05:50.098+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown initiated...
2025-03-03T15:05:50.116+0100 [main] INFO  com.zaxxer.hikari.HikariDataSource - HikariPool-1 - Shutdown completed.
java.lang.AssertionError: KBS Pin appeared to matched but reg lock still failed!
	at org.asamk.signal.manager.util.NumberVerificationUtils.verifyNumber(NumberVerificationUtils.java:138)
	at org.asamk.signal.manager.internal.RegistrationManagerImpl.verifyAccount(RegistrationManagerImpl.java:163)
	at org.asamk.signal.commands.VerifyCommand.verify(VerifyCommand.java:71)
	at org.asamk.signal.commands.VerifyCommand.handleCommand(VerifyCommand.java:43)
	at org.asamk.signal.commands.CommandHandler.handleRegistrationCommand(CommandHandler.java:33)
	at org.asamk.signal.App.handleRegistrationCommand(App.java:268)
	at org.asamk.signal.App.handleCommand(App.java:177)
	at org.asamk.signal.App.init(App.java:147)
	at org.asamk.signal.Main.main(Main.java:56)

This may or may not be connected to the encryption issues aI have #1719, but as I found no issue for it yet I thought it might be an edge case that could use attention. Or I'll just wait out the timer...