refactor: improve bounty ordering logic in BountyLive

- Updated the ordering of bounties in the `BountyLive` module to prioritize the current organization, enhancing the relevance of displayed bounties.
- Removed a TODO comment regarding pooling bounties for better code clarity.

Author: zcesur

lib/algora_web/live/bounty_live.ex

@@ -104,9 +104,8 @@ defmodule AlgoraWeb.BountyLive do
         where: u.provider_login == ^repo_owner,
         where: r.name == ^repo_name,
         where: t.number == ^number,
-        # TODO: pool bounties
-        limit: 1,
-        order_by: [asc: b.inserted_at]
+        order_by: fragment("CASE WHEN ? = ? THEN 0 ELSE 1 END", u.id, ^socket.assigns.current_org.id),
+        limit: 1
       )
       |> Repo.one()
       |> Repo.preload([:owner, :creator, :transactions, ticket: [repository: [:user]]])