compose test: Check ID still included if same-name users deactivated

While autocomplete does not include deactivated users, there still
is a possibility that same-name users with one or more deactivated
gets mentioned, which will make the mentioned user ambiguous without
the id, this is explained in #451.

This adds a test case that asserts same-name users are disambiguated
while composing the message regardless of them being active.

Fixes part of #451

Author: Khader-1

test/example_data.dart

@@ -59,6 +59,7 @@ User user({
   int? userId,
   String? email,
   String? fullName,
+  bool? isActive,
   String? avatarUrl,
   Map<int, ProfileFieldUserData>? profileData,
 }) {
@@ -68,7 +69,7 @@ User user({
     email: email ?? '[email protected]', // TODO generate example emails
     fullName: fullName ?? 'A user', // TODO generate example names
     dateJoined: '2023-04-28',
-    isActive: true,
+    isActive: isActive ?? true,
     isOwner: false,
     isAdmin: false,
     isGuest: false,

test/model/compose_test.dart

@@ -316,6 +316,11 @@ hello
       store.addUsers([user, eg.user(userId: 5), eg.user(userId: 234, fullName: user.fullName)]);
       check(mention(user, silent: true, users: store.users)).equals('@_**Full Name|123**');
     });
+    test('`users` passed; has two same-name users but one of them is deactivated', () {
+      final store = eg.store();
+      store.addUsers([user, eg.user(userId: 5), eg.user(userId: 234, fullName: user.fullName, isActive: false)]);
+      check(mention(user, silent: true, users: store.users)).equals('@_**Full Name|123**');
+    });
     test('`users` passed; user has unique fullName', () {
       final store = eg.store();
       store.addUsers([user, eg.user(userId: 234, fullName: 'Another Name')]);