Disable async activation for channel types not showing config page

[norkans7]

The channel types do not have a config UI page so when activate fails, the channel is useless, this change will release the channel so the use can claim that again

rapidpro/temba/channels/models.py

Lines 406 to 415 in a89ae1c

	if channel_type.async_activation:
	on_transaction_commit(lambda: channel_type.activate(channel))
	else:
	try:
	channel_type.activate(channel)
	except Exception as e:
	# release our channel, raise error upwards
	channel.release(user)
	raise e

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (a89ae1c) to head (bb549bb).

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #5662   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          565       565           
  Lines        25835     25839    +4     
=========================================
+ Hits         25835     25839    +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

---

🚨 Try these New Features:

• Flaky Tests Detection - Detect and resolve failed and flaky tests

[rowanseymour]

@norkans7 remind me again, the point of async_activation is that a channel can call back to us and the channel will definitely exist in the db? Or that we need a channel to have uuid/id when we activate it? Are we sure these types don't require that?

[norkans7]

@rowanseymour We need the UUID as most of the time that is used for the URL we send in when setting the webhook URL
so the channel need to be in the DB
And we just made those activation request in the background task
The issue is when that activation fail, the channel in the DB is useless

Some channel types such as D3C still have the config page and the user can go and manually set the webhook URL, for these we they cannot manually set the URL so we do not show the config page, so I think in case the activation fail we clean up the DB object by releasing that.