perf(core): optimization for assignToChannels method

[monrostar]

Description

This is an optimization of the channel-aware update request for Entity. The method offers 3 separate queries without additional data processing by TypeORM.

1. Get the object without unnecessary links and check that it exists.
2. Make a separate, more optimized query into the ManyToMany table to reduce the amount of data to process
3. Change the save method to Remove or Add (unbinds, binds) given value from entity relation.

relation('channels')
.of(entity.id)
.add(newChannelIds) or .remove(existingChannelIds);

Breaking changes

No

Checklist

📌 Always:

• I have set a clear title
• My PR is small and contains a single feature
• I have checked my own PR

👍 Most of the time:

• I have added or updated test cases
• I have updated the README if needed

[michaelbromley]

With the latest updates we explicitly added inverse relations to the Channel entity.

I'm wondering what would happen if someone defines a custom channel-aware entity which does not have the inverse relation on the Channel? Would this break?

[monrostar]

This is quite normal, there should be no errors because even without reverse side entity is still available
But if there are problems we replace them with pure SQL

With the latest updates we explicitly added inverse relations to the Channel entity.

I'm wondering what would happen if someone defines a custom channel-aware entity which does not have the inverse relation on the Channel? Would this break?

[monrostar]

or just manually parse the column names in the table. This can also be done. We just need to test it on a real project