fix: adapt to new Baimiao API v2 with OSS upload

[zeta987]

Fixes #3

Problem

Baimiao web API has changed. The old dataUrl inline upload no longer works:

{
  "code": 0,
  "data": {
    "hash": "8591a..."
  },
  "msg": "图片上传出错，请强制刷新网页后重试"
}

Solution

Adapt to the new API flow: upload image to Aliyun OSS first, then pass fileKey to OCR endpoint.

[CaptainMusX]

If you fill in the cell phone number, it will be recognized incorrectly, here you can automatically select the cell phone number and email address according to the presence or absence of "@".

[cenaia]

If you fill in the cell phone number, it will be recognized incorrectly, here you can automatically select the cell phone number and email address according to the presence or absence of "@".

Maybe there was a problem. A few minutes ago, I tried to sign in with my email and phone number, but it kept saying “邮箱地址不正确.” After a few minutes, I was able to sign in with my email.

[zeta987]

Implemented in <3703ed8>.
Login type is now auto-detected:

• use "email" when username contains "@"
• otherwise use "mobile"
  Thanks for the suggestion.

[zeta987]

If you fill in the cell phone number, it will be recognized incorrectly, here you can automatically select the cell phone number and email address according to the presence or absence of "@".

Maybe there was a problem. A few minutes ago, I tried to sign in with my email and phone number, but it kept saying “邮箱地址不正确.” After a few minutes, I was able to sign in with my email.

Based on testing, the login issue can be resolved by clearing the residual plugin data. This can be accomplished using either of the following methods:

Method 1: Reinstall via Application

1. Completely remove the plugin within the pot app.
2. Restart the application.
3. Reinstall the plugin.

Method 2: Manually Delete the Plugin Directory

1. Close the pot app.
2. Delete the following directory:
   %APPDATA%\com.pot-app.desktop\plugins\recognize\plugin.com.TechDecryptor.baimiao_ocr
3. Restart the application and reinstall the plugin.

Performing either step clears the cached configuration and restores normal login functionality.