Show message when moving between components while translating

[abhinavohri]

Fixes #14798

When translating on category or project level, make user aware if the component of unit changes.

[nijel]

Do you see a reasonable way to make it work without passing this info in request? The long-term plan is to use unit URLs while navigating (see #9953).

[nijel]

This will crash with a blank value (form_offset=).

[nijel]

Name is not good enough here as it does not have to be unique, at least categories should be included. Perhaps using full component name including project would be better for consistency with other views.

[codecov]

Codecov Report

❌ Patch coverage is 33.33333% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 91.14%. Comparing base (8b8a288) to head (3594817).
⚠️ Report is 3376 commits behind head on main.

Files with missing lines	Patch %	Lines
weblate/trans/views/edit.py	33.33%	3 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #14921      +/-   ##
==========================================
+ Coverage   91.10%   91.14%   +0.03%     
==========================================
  Files         624      626       +2     
  Lines       65338    65476     +138     
  Branches     6746     6753       +7     
==========================================
+ Hits        59527    59676     +149     
+ Misses       4077     4069       -8     
+ Partials     1734     1731       -3     

Files with missing lines	Coverage Δ
weblate/trans/views/edit.py	81.17% <33.33%> (-0.56%)	⬇️

... and 46 files with indirect coverage changes

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nijel]

This should be pinned to the search result; otherwise it will have too many corner cases:

• Translating one project, then starting translating another project would yield the message.
• Opening multiple translation tabs they will fight for the same previous_unit_id.

It could be stored inside the search data, which we already have in the search function above.

[abhinavohri]

okay

[nijel]

Merged, thanks for your contribution!