Change Details

This diff introduces the following changes to the internal notifications library: - Removing the old FFI return type (we are using it to call the Rust from C++, but now it doesn't needed as we are calling Rust from Rust) and using the Rust native `Result` instead with the `Ok` and our custom error types `ApnsErrors` and `FcmErrors` because we want to distinguish token-related errors and request the new token from the client. - Using the static `CONFIG` parameters from the D5641 instead of passing config parameters on every notification-sending call. Linear task: [[ https://linear.app/comm/issue/ENG-1893/rust-part-code-small-refactors | ENG-1891 ]]

This diff introduces the following changes to the internal notifications library: - Removing the old FFI return type (we are using it to call the Rust from C++, but now it doesn't needed as we are calling Rust from Rust) and using the Rust native `Result` instead with the `Ok` and our custom error types `ApnsErrors` and `FcmErrors` because we want to distinguish token-related errors and request the new token from the client later. - Using the static `CONFIG` parameters from the D5641 instead of passing config parameters on every notification-sending call. Linear task: [[ https://linear.app/comm/issue/ENG-1893/rust-part-code-small-refactors | ENG-1891 ]]

This diff introduces the following changes to the internal notifications library: - Removing the old FFI return type (we are using it to call the Rust from C++, but now it doesn't needed as we are calling Rust from Rust) and using the Rust native `Result` instead with the `Ok` and our custom error types `ApnsErrors` and `FcmErrors` because we want to distinguish token-related errors and request the new token from the client later. - Using the static `CONFIG` parameters from the D5641 instead of passing config parameters on every notification-sending call. Linear task: [[ https://linear.app/comm/issue/ENG-1893/rust-part-code-small-refactors | ENG-1891 ]]