For #26190 - Update jump back in cfr logic and message

[Alexandru2909]

Updated message and logic for jump back in onboarding message.

Pull Request checklist

• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not
• Accessibility: The code in this PR follows accessibility best practices or does not include any user facing features. In addition, it includes a screenshot of a successful accessibility scan to ensure no new defects are added to the product.

QA

• QA Needed

To download an APK when reviewing a PR (after all CI tasks finished running):

1. Click on Checks at the top of the PR page.
2. Click on the firefoxci-taskcluster group on the left to expand all tasks.
3. Click on the build-debug task.
4. Click on View task in Taskcluster in the new DETAILS section.
5. The APK links should be on the right side of the screen, named for each CPU architecture.

GitHub Automation

Fixes #26190

[MozillaNoah]

where is this number derived from?

[Alexandru2909]

For the maxWidth and maxHeight values, my intention was to respect the Figma values.

Here are a couple of screenshots:

Current	After

Should we stick with the maxWidth = 200dp and wrap_content height instead? We could also file a ticket to use the compose CFR to achieve this behavior.

[MozillaNoah]

For the height, I'd normally lean towards wrap_content so text can expand on small devices or devices with larger fonts without being cut-off.

For the width, I'd double check with UX to see if this is supposed to be a fixed width or wrap.

[Alexandru2909]

Tagging @Kate-Galetski to check whether the CFR should respect the design's width (see After picture in the previous comment) or the current CFR width.

[Kate-Galetski]

Hi @Alexandru2909 the width looks fine to me! (atm we don't have any strict rules to how much % of the page the CFR should expand to.) What doesn't look fine to me is that this CFR is glued to the left border of the screen, while it actually should have a padding of 12px in there. Link to figma
@gabrielluong do we need a separate ticket for that adjustment as well?

[Alexandru2909]

This seems like a minor change so I added it in this ticket. In the figma designs, Android code tool indicates the value as dp, so here is an updated screenshot:

If this should be addressed in another ticket we could also maintain the current maxWidth and update it in the CFR design issue.

[gabrielluong]

I am accepting these values since Kate has ok'd them. However, I would ask that you test this with a different language (say German) to see if we need any further followup.

[Alexandru2909]

I tested with multiple languages and the CFR looks fine, apart from the rtl languages, as they use the end padding and make the CFR look glued to the left edge of the screen. For this I added the 12dp padding to the end too.

[gabrielluong]

Please test the CFR to see how it looks like with a different language (ex, German) prior to landing.

[mergify]

This pull request has conflicts when rebasing. Could you fix it @Alexandru2909? 🙏