user/fetcher: drop nonsense type-based follow update skip

The real intent behind the commit introducing this seemed to have been
avoiding running this when the actor does not expose follow collection ids
ec24c70db8.
This is already taken care of with the :collections_available check.
Some Implementations use other actor type like Group etc for visible,
followable actors making skipping undesirable.

Notably though, this actually has _always_ skipped counter updates
as even when this check was introduced, the user changeset data and
struct used the :actor_type key not :type.

In some situations fetch_follow_information_for_user is called directly
from other modules thus occasionally counters still got updated
for accounts with closer federation relationships masking the issue.

lib/pleroma/user/fetcher.ex

@@ -190,7 +190,6 @@ defmodule Pleroma.User.Fetcher do
 
   def maybe_update_follow_information(user_data) do
     with {:enabled, true} <- {:enabled, Config.get([:instance, :external_user_synchronization])},
-         {_, true} <- {:user_type_check, user_data[:type] in ["Person", "Service"]},
          {_, true} <-
            {:collections_available,
             !!(user_data[:following_address] && user_data[:follower_address])},

test/pleroma/user/fetcher_test.exs

@@ -421,18 +421,6 @@ defmodule Pleroma.User.FetcherTest do
              end) =~ "Follower/Following counter update for #{user.ap_id} failed"
     end
 
-    test "just returns the input if the user type is Application", %{
-      user: user
-    } do
-      user =
-        user
-        |> Map.put(:type, "Application")
-
-      refute capture_log(fn ->
-               assert ^user = Fetcher.maybe_update_follow_information(user)
-             end) =~ "Follower/Following counter update for #{user.ap_id} failed"
-    end
-
     test "it just returns the input if the user has no following/follower addresses", %{
       user: user
     } do