Fix #10511 - make correct redirect to Opportunity's DetailView without extra data from submitted form

[mubat]

Fixed issue #10511.

Description

Issue happens because user not redirected to other page but submitting form on "Contact-Opportunity" page with other form data that should send at request. And this data wrongly adds to search queries because SubPanel class uses SeacrhForm functionality to filter data and SearchForm grubs data from $_POST that should happens for subpanels. Thats why it includes contact_name and contact_id to SQL that doesn't include this tables and shouldn't filter by these params.
Example of wrongly generated SQL:

SELECT count(*) c FROM meetings  LEFT JOIN meetings_cstm ON meetings.id = meetings_cstm.id_c  INNER JOIN  opportunities meetings_rel ON meetings.parent_id=meetings_rel.id AND meetings_rel.deleted=0
 AND meetings.parent_type = 'Opportunities'
 where ( meetings.parent_id='37f91d5123-4123b-1e77-c115-66ba1b2a814c' AND (meetings.status !='Held' AND meetings.status !='Not Held') AND (( contacts.first_name like 'John23 test%' OR contacts.last_name like 'John23 test%' ))) AND meetings.deleted=0 )  

Steps to reproduce issue

1. Open DetailView of some Opportunity that has linked Contact at subpanel
2. Expand 'Contacts', 'History' and 'Activities' subpanels
3. Click 'Edit' on Contact at subpanel
4. It opens custom page to manage role of the Contact at Opportunity
5. Click "Cancel"
6. It returns to Opportunity's DetailView

[ER]: all subpanels works fine without errors and print linked data
[AR]: have message at some subpanels "Database failure. Please refer to suitecrm.log for details."

Motivation and Context

This bug breaks business logic at out company. Extra data from "Contact-Opportunity" form should send to Opportunity's DetailView page.
This PR fixed issue with broken subpanels on Opportunity DetailView, one of the most common modules.

How To Test This

Open "Contact-Opportunity" page from Contacts subpanel and click "Cancel".

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Final checklist

• My code follows the code style of this project found here.
• My change requires a change to the documentation.
• I have read the How to Contribute guidelines.

[SuiteBot]

All committers have signed the CLA.

[serhiisamko091184]

Hello @mubat!

Thanks for your contribution!

Regards,
Serhii