Transfer a project/group to a new namespace inheriting integrations

What does this MR do?

After launching group-level integrations &2543 in %13.6, we are improving the functionality. In this case, transfer a project/group under a new namespace implies inheriting the integrations of the new group.

The approach to transfer a project/group under a new namespace (group) is the following:

1. Remove the current services.
2. Re-create them again (now with the new settings if they exist under the new group).
3. For groups, propagate the new settings to subgroups and projects belonging to the group.

It also excludes overriding integration with custom values.

---

I've also reduced the total number of query counts used in the specs.

Related to #255923 (closed)