Remove redundant null-aware operator in test

[sidrao2006]

:sparkles: What kind of change does this PR introduce? (Bug fix, feature, docs update...)

Test refactor

:arrow_heading_down: What is the current behavior?

Uses null aware operator

:new: What is the new behavior (if this is a feature change)?

Replace ?. with .

:boom: Does this PR introduce a breaking change?

No

:bug: Recommendations for testing

N/A

:memo: Links to relevant issues/docs

N/A

:thinking: Checklist before submitting

• [x] All projects build
• [x] Follows style guide lines (code style guide)
• [ ] Relevant documentation was updated
• [ ] Rebased onto current develop

[renefloor]

Hmmm.. I wanted to approve and merge, however this will mean that any update is only compatible with Flutter 3 and higher. Only for a warning in this test I would not want to have that.