Remove DB transaction when creating issues - GitHub Import
When GitHub Import creates issues, it uses a transaction block. However, there is an issue with this approach: long-running tasks are also inside the transaction block, which can cause the database connection to be held for an extended period of time. For example, inside the transaction block, API requests are made to fetch user details, which is not a good practice.
In fact, due to the API requests made inside the transaction associated with the change introduced by !140051 (merged) and !141826 (merged), gitlab-com/gl-infra/production#17504 (closed) incident was caused.
Proposed solution
Analyse if the use of transaction block is necessary. If not, let's remove it.
If we believe the transaction block is necessary, let's move long-running tasks outside the transaction block.