Fix #10365: Custom subpanels not loading data until the page is reloaded

[pablonr11]

This fixes a bug that makes custom subpanels that uses $this->_focus->id as a function parameter not load correctly

Description

By adding the record Id to the getBean call the data for the current record is retrieved which allows the layout_def custom function to acceed the bean data for building a custom query correctly.

Motivation and Context

This reduces the error margin when creating custom subpanels for modules. Also prevents the user need to reload the page everytime a custom subpanel is opened.

How To Test This

1. Create a custom layout_def subpanel for any module that uses a custom subpanel to build a query with $this->_focus->id as a function parameter.
2. Use this parameter in your query
3. This will make the subpanel not load when opening it for the first time or when trying to order the subpanel by some column from the view.

Types of changes

• [x] 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

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

[SuiteBot]

This pull request has been mentioned on SuiteCRM. There might be relevant details there:

https://community.suitecrm.com/t/custom-subpanel-sorting-bug/91946/10

[SuiteBot]

This pull request has been mentioned on SuiteCRM. There might be relevant details there:

https://community.suitecrm.com/t/adding-records-to-history-subpanel/90101/10

[pstevens71]

If I can add my 2 cents. I just tested this in my dev to fix the sorting of a custom subpanel. So far so good!