[FIX] web: read_group RPC

[nim-odoo]

Example of failing request:

rpc.query({
    model: 'link.tracker.click',
    method: 'read_group',
    args: [[links_domain, ['create_date', '>', interval]], ['country_id']],
    kwargs: {groupby:'country_id'},
});

The RPC request built contains the following:

args: [[["link_id", "=", 1]], ["create_date"]]
kwargs: {groupby: "create_date:day", domain: [], fields: []}

This will be interpreted server side as:

model.read_group([['link_id', '=', 1]], ['create_date'], groupby=['create_date:day'], domain=[], fields=[])

2 arguments match domain and fields, which causes a crash.

opw-781300

Description of the issue/feature this PR addresses:

Current behavior before PR:

Desired behavior after PR is merged:

--
I confirm I have signed the CLA and read the PR guidelines at www.odoo.com/submit-pr

[ged-odoo]

good. But if you feel like it, the same fix should be done with the search_read method, just below

[nim-odoo]

@ged-odoo hum yeah, but in the case of search_read:
params.kwargs.domain = options.domain || params.domain || params.kwargs.domain;

So here if no kwargs are specified, [] won't be added by default. So I guess if you end up in this situation, it means that you have written something incorrect such as:

rpc.query({
    model: 'link.tracker.click',
    method: 'read_group',
    args: [
        [['create_date', '>', interval]]
    ],
    kwargs: {domain: ['create_date', '>', interval]},
});

In this case I would blame the calling method, not the framework.