[Issue] Allow backend login without redirect

[m2-assistant]

This issue is automatically created based on existing pull request: #30950: Allow backend login without redirect

---

Description (*)

Magento 2.4-develop
Currently, when accessing a backend page via a direct URL as a logged out admin, the admin is redirected to <backend-url>/admin to log in. After logging in, they are redirected to the admin dashboard (or whatever page is selected as the startup page in system configuration).

This can be frustrating, since the admin now has to manually navigate to the requested page. This also potentially prevents some scripted tasks.

This PR proposes to remove the redirect to <backend-url>/admin, in which case the log in happens on the same page as the requested page (same as M1). The user is directly redirected to the requested page after login.

Related Pull Requests

• MAGETWO-45465 The proposed code to be removed was added in this commit.

Manual testing scenarios (*)

1. Add an admin user with a role that allows them to view products (Magento_Catalog::products ACL resource).
2. Make sure you're logged out from the backend.
3. Attempt to access <backend-url>/catalog/product/
4. The login form should be presented to you. Check the URL - you should still be on <backend-url>/catalog/product/ with this PR.
5. Log in.
6. You should see the product listing directly (and not be redirected to the startup page).

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds are green)

[TheRealHunzik]

FInally, Magento Team has Started working on this issue as it was really frustrating

[m2-assistant]

Hi @engcom-Delta. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[magento-engcom-team]

✅ Confirmed by @engcom-Delta
Thank you for verifying the issue. Based on the provided information internal tickets MC-40241 were created

Issue Available: @engcom-Delta, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.