feat!: migrate firebase_remote_config nullsafety

[daniloadorno]

No description provided.

[google-cla]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[rrousselGit]

Thanks! Could you fix the lint errors? https://github.com/FirebaseExtended/flutterfire/pull/5397/checks?check_run_id=2148189173

[Salakar]

I think the Analytics portion of this PR may be a duplicate of the work being done on #5341 - can we perhaps remove it from this PR and focus on just Remote Config here? Thoughts @rrousselGit?

[IchordeDionysos]

@Salakar @rrousselGit also in this PR are the same issues that @rrousselGit mentioned that I already fixed in my PR :)

[Salakar]

@Salakar @rrousselGit also in this PR are the same issues that @rrousselGit mentioned that I already fixed in my PR :)
@IchordeDionysos

Let's focus on Remote config for this PR - @daniloadorno would you mind removing the analytics portions of this pull request - thanks.

[b-jan]

@daniloadorno I saw you worked on the migration. Is it ready ?

[daniloadorno]

@daniloadorno I saw you worked on the migration. Is it ready ?

yes

[rrousselGit]

Could you format and fix the test step?

[daniloadorno]

Could you format and fix the test step?

done

[rrousselGit]

Why are these tests commented?

[daniloadorno]

they refer to the old implementation without nullsafety and have errors in their execution

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[google-cla]

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

[Zeswen]

@rrousselGit I believe there's a problem with @daniloadorno's commits. It seems like he commited changes with an alter account not related to GitHub and the Google checks are not passing.

Any thoughts?

[daniloadorno]

@rrousselGit #5686