[5.3] Fix field group permission check

[joomdonation]

Pull Request for Issue #44542.

Summary of Changes

Currently, the GroupModel model uses wrong asset name for permission check, so permission checking for field groups does not work at all. The right name of assist is something like com_content.fieldgroup.20 but we are checking using com_content.article.fieldgroup.20 . This PR fixes that wrong behavior

Testing Instructions

• Use Joomla 5.3
• Create a new field group for Content. Look at Permissions tab, set Edit State permission of that field for Administrator user group to Denied.
• Save it.
• Logout, then login using an Administrator account.
• Check on the checkbox next to the field group and try to use Publish button in the toolbar to publish that
• Try to click on field group to edit

Actual result BEFORE applying this Pull Request

You can publish field group, although Administrator does not have permission to do that.
You can change value for Published field of the field group

Expected result AFTER applying this Pull Request

• There is an error message when try to publish that field group
• You are not allowed to change Published field for the field group

Link to documentations

Please select:

• Documentation link for docs.joomla.org:

• No documentation changes for docs.joomla.org needed

• Pull Request link for manual.joomla.org:

• No documentation changes for manual.joomla.org needed

[crommie]

I have tested this item ✅ successfully on 3a9733f

Followed instructions, works as described

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44956.}

[komalm]

I have tested this item ✅ successfully on 3a9733f

Expected Results After Applying the Patch
The Published field should be disabled or inaccessible when editing the field group

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44956.}

[joomdonation]

RTC. Thanks for testing.

---

_{This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/44956.}