Navigate the poem tree instead of the visit history

Breadcrumbs: a poem's path (poet » book » section) is now built from its own
fullTitle and fullUrl and every ancestor is tappable, so the trail is the same
whether the poem was opened by browsing, from the saved list, from a
breadcrumb, or by reading on from the previous poem.

Back: browsing is a tree, so Back climbs it — poem to section to book to poet
to home — rather than retracing however you arrived. Each screen derives its
own parent from its URL and navigation keeps the stack flat, which is what
stops Back from walking forward again into the page you just left. System Back
and the top-bar arrow do the same thing.

The exception is a poem opened from the saved list: that was reached from a
list, not a shelf, so Back returns to the list, and reading on through the
divan keeps that origin.

Plus a Home button on every screen below the poet list.

Verified on an API 36 emulator: drilled Hafez > ghazals > ghazal 3 and walked
back up to the poet list, and opened a saved Khayyam rubai and confirmed Back
returns to the saved list rather than the poet's section.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

app/src/main/res/values-fa/strings.xml

@@ -48,4 +48,5 @@
     <string name="copy">رونوشت</string>
     <string name="copied">رونوشت شد</string>
     <string name="download_selected">دریافت %d شاعر</string>
+    <string name="home">خانه</string>
 </resources>

app/src/main/res/values-ur/strings.xml

@@ -48,4 +48,5 @@
     <string name="copy">نقل کریں</string>
     <string name="copied">نقل ہو گیا</string>
     <string name="download_selected">%d شعرا ڈاؤن لوڈ کریں</string>
+    <string name="home">ہوم</string>
 </resources>

app/src/main/res/values/strings.xml

@@ -53,4 +53,5 @@
     <string name="next_poem">%s ›</string>
     <string name="previous_poem">‹ %s</string>
     <string name="download_selected">Download %d poets</string>
+    <string name="home">Home</string>
 </resources>