Improve and standarize Navigation API

[ulisesmac]

Problem

Taken from @briansztamfater 's comment:

Description

[...] it is confusing to have navigation effects and events with same naming, like

status-mobile/src/status_im/navigation/events.cljs

Line 55 in 972a88e

{:events [:navigate-back]}

and

status-mobile/src/status_im/navigation/effects.cljs

Line 91 in 602b271

(rf/reg-fx :navigate-back

.......
or
.......

status-mobile/src/status_im/navigation/events.cljs

Line 34 in 972a88e

{:events [:navigate-to-within-stack]}

and

status-mobile/src/status_im/navigation/effects.cljs

Line 78 in 602b271

(rf/reg-fx :navigate-to-within-stack navigate-to-within-stack)

We should rename events to have navigation / namespace prefix as per our guidelines

status-mobile/doc/new-guidelines.md

Lines 364 to 372 in 5cc027a

	### Subscription names and event names
	Always register events and subscriptions using a meaningful namespace, but don't
	namespace them with `::`. We understand it's a controversial decision because
	there are both pros and cons to such practice.
	Whenever appropriate, it's also recommended to use _fake_ namespaces to convey
	more knowledge in the keyword about which bounded context (domain) it refers to.
	You may also use dots to convey hierarchical structures.

so events are like :navigation/navigate-back, :navigation/navigate-back-to, :navigation/navigate-to, :navigation/navigate-to-within-stack, etc, or even better they could be improved as :navigation/pop, :navigation/pop-to, :navigation/push, :navigation/push-within-stack, etc, to comply with common nomenclature for stack navigations

[ulisesmac]

@briansztamfater I'm adding this as an issue so that it's addressed 👍

[ilmotta]

@ulisesmac @brianfernalld FYI: I left navigation effects on purpose out of this PR #18047 to reduce the chance of regressions from a single PR.

We have a new guideline, which I believe has not being solidified in develop yet, where re-frame effects should start with the qualification :effects. This by itself should help differentiate events from effects that have similar or even identical names. You can search in the repo to find many examples.

From this guideline, we would use the keyword :effects.navigation/navigate-within-stack, but that's a mouthful 🤷🏼 We sometimes use very long names in this repo! We could use a little bit of conciseness in widely used names. For instance, nav is a pretty decent abbreviation for navigation.

But anyway, just wanted to share about the PR and the guideline for effect names.