profiling(fix): use an unpadded base64 encoding (#1749)

Recently we switched to a new crate for `base64` data encoding/decoding
(#1743).

In doing so, a regression that discards unpadded base64 profiles was
introduced.

This PR restores the expected behaviour. 

#skip-changelog

relay-profiling/src/android.rs

@@ -2,7 +2,7 @@ use std::collections::{HashMap, HashSet};
 
 use android_trace_log::chrono::{DateTime, Utc};
 use android_trace_log::{AndroidTraceLog, Clock, Time, Vm};
-use data_encoding::BASE64;
+use data_encoding::BASE64_NOPAD;
 use serde::{Deserialize, Serialize};
 
 use relay_general::protocol::EventId;
@@ -91,7 +91,7 @@ impl AndroidProfile {
     }
 
     fn parse(&mut self) -> Result<(), ProfileError> {
-        let profile_bytes = match BASE64.decode(self.sampled_profile.as_bytes()) {
+        let profile_bytes = match BASE64_NOPAD.decode(self.sampled_profile.as_bytes()) {
             Ok(profile) => profile,
             Err(_) => return Err(ProfileError::InvalidBase64Value),
         };