Regression: Change names of requested apps sorting options

[rique223]

Proposed changes (including videos or screenshots)

Jira task: MKP-253

Changed the name of the requested app-related sorting options to cause less confusion regarding their expected behavior and solved some UX problems with the initial state of the sorting filter when on different marketplace pages. Also fixed some typos.
Demo image:

Issue(s)

Steps to test or reproduce

Further comments

[codecov]

Codecov Report

Merging #28312 (5299324) into develop (9114f28) will decrease coverage by 0.02%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           develop   #28312      +/-   ##
===========================================
- Coverage    44.94%   44.92%   -0.02%     
===========================================
  Files          771      771              
  Lines        14979    14979              
  Branches      2092     2092              
===========================================
- Hits          6732     6730       -2     
- Misses        7950     7951       +1     
- Partials       297      298       +1     

Flag	Coverage Δ
e2e	44.89% <ø> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[dougfabris]

why not JUST check if isRequested on the initial setSortFilterStructure?
no need at all for this useEffect

[rique223]

why not JUST check if isRequested on the initial setSortFilterStructure?
no need at all for this useEffect

Because what you are describing, if I understood correctly, would only work on the first access of this component and would not change to the "unread requested first" sorting when accessing the requested apps page.