[PM-23785] Use actual error types in UniFFI

[dani-garcia]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-23785

📔 Objective

Currently all the UniFFI errors get serialized as a string. This PR updates UniFFI to the latest main changes to add support for proper errors. This requires a couple of changes:

• I've tagged all the errors with uniffi::Error and added support to the bitwarden-error macro for uniffi.
• I've had to add some workaround code to deal with an edge case that caused some compilation issues, more info upstream: Wrong Android error name when using nested external error mozilla/uniffi-rs#2636
• Updated the gradle wrapper included as the old version was having some issues with my java version

How this looks on the mobile apps:
Android:

try {
    client.crypto().deriveKeyConnector(request)
} catch (ex: BitwardenException.DeriveKeyConnector) {
    when (ex.v1) {
        is DeriveKeyConnectorException.WrongPassword -> {
            println("That is the wrong password: $ex")
        }
        else -> {
            println("Other bitwarden error: ${ex.v1}")
        }
    }
} catch (ex: BitwardenException) {
    println("Other bitwarden error: $ex")
}

iOS:

do {
    try client.crypto().deriveKeyConnector(request);
} catch(BitwardenError.DeriveKeyConnector(DeriveKeyConnectorError.WrongPassword(let msg))) {
    print("Wrong password:", msg)
} catch {
    print("Other bitwarden error:", error)
}

⏰ 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

[dani-garcia]

The latest UniFFI doesn't allow default trait methods, so I've removed it. We weren't using it anyway.

[dani-garcia]

Note that this is different than what WASM is doing. The WASM part is generating the code based on the wasm feature flag of the macro crate itself, while the UniFFI is always emmitting the cfg_attr code, which means it's the feature flag of the final crate that gets evaluated.

I've needed to do this because I couldn't quite get it working the other way, I think the workspace feature unification was causing issues and generating the UniFFI code all the time, even when not needed (like for the bitwarden-ipc crate).

Doing it this new way has one negative effect, which is that it's not obvious that the final crate has to have a uniffi feature, and otherwise you'll get a warning (that I've had to silence in the root cargo.toml because of wasm-only crates like bitwarden-ipc)

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud