A notification told alone names its group

v1 notifications, and those a stream tells, carried an 'ungrouped' key, so
a client reading grouped notifications could not fold a new like into the
group of likes it already shows. Each now names the group it belongs to by
default (likes and boosts of one post, follows within an hour).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01LsXgEaXee4GCU1hwYgPJXw

PrivaPub/Api/Mastodon/Controllers/TimelinesController.cs

@@ -206,11 +206,11 @@ namespace PrivaPub.Api.Mastodon.Controllers
 
 		// Grouped notifications (Mastodon 4.3): api_versions.mastodon says we speak that API, so clients call it. Likes and
 		// boosts of one post group together, as do follows within an hour; everything else stands alone.
-		static readonly HashSet<string> DefaultGrouped = new() { "favourite", "reblog", "follow" };
+		internal static readonly HashSet<string> DefaultGrouped = new() { "favourite", "reblog", "follow" };
 
 		HashSet<string> Grouped() => Params.List("grouped_types") is { Count: > 0 } chosen ? chosen.ToHashSet() : DefaultGrouped;
 
-		static string GroupKey(NotificationEntity n, ISet<string> grouped) =>
+		internal static string GroupKey(NotificationEntity n, ISet<string> grouped) =>
 			!grouped.Contains(Names[n.Type]) ? $"ungrouped-{n.ID}"
 			: n.Type == NotificationType.Follow ? $"grouped-follow-{n.CreatedAt:yyyyMMddHH}"
 			: string.IsNullOrEmpty(n.PostId) ? $"ungrouped-{n.ID}"