feat: add an argument to expand moreInfo of an input

[hetangmodi-crest]

Added an argument in get_more_info function which specifies whether to click on the arrow that display more info about an input.
This is required in a scenario as described in splunk/addonfactory-ucc-generator#1410.

[sgoral-splunk]

I know it's simple change but maybe its worth to add some simple test just to test if it really skips the click? smth with pytest.raises etc.? What do you think?

[vtsvetkov-splunk]

I don't get the point of this flag. It seems like leaking abstraction for the method that should return the content of _More Info`. Why should caller of this method know about if it is open or close?

Here is my suggestion

1. check if the row is expanded with attribute aria-expanded.
2. if the value is 'false', click on the arrow
3. if there is a Loading inside, wait it disappear (in case the custom row is used), it loads in runtime

Here is how I would write in UI unit tests

    const arrow = within(inputRow).getByRole('cell', { name: /expandable/i });
    const isExpanded = arrow.getAttribute('aria-expanded');
    if (isExpanded === 'false') {
        await userEvent.click(arrow);
    }
    await waitFor(() => expect(arrow.getAttribute('aria-expanded')).not.toBe('false'));
    const loading = screen.queryByText('Loading...');
    if (loading) {
        await waitForElementToBeRemoved(loading);
    }

[rohanm-crest]

We added the flag to ensure that the moreInfo section remains expanded based on the use case. This allows any changes made to the input's row to be immediately reflected in the custom row section without collapsing and re-expanding the moreInfo section.

[rohanm-crest]

I have written the unit test case in my PR itself, so we don't need this change in smartx. Hence, we can close this PR.

[hetangmodi-crest]

Added unit test cases for get_more_info function for expand_row parameter.

[rohanm-crest]

Test case is covered in the PR PR-1445 so don't need this smartx changes. Hence, closing this PR.