Allianceauth-afat

Changed

- Admin views are now searchable
- Manual log removed from admin view. This should be migrated by now to the new
combined log. If you haven't done so yet, see
[update instructions for v2.0.0](-update-instructions-for-v200-) please

Changed

- JS modernized
- FAT link hash creation, to ensure the hash is definitely unique (Not that it
wasn't before, but now it is enforced via its DB table field)

Fixed

- Using Django application registry instead of directly accessing `INSTALLED_APPS`
- Using Django messages API (86)

Added

- Index to `hash` field in AFatLink model (Thanks ErikKalkoken)

Changed

- Time period (year and month select) templates refactored
- FAT link hashes in log are now linked to their respective FAT link details, as
long as the FAT link is not deleted yet (Thanks to ErikKalkoken to let me know
how to do so without firing potentially hundreds of queries against the database)
- Reduced load time for all pages incl. admin site (Thanks ErikKalkoken)

Added

- Button to close your own ESI fleet to more view. It is now available on the
Dashboard, in the FAT link list and in the FAT link details view as well. You can
only close your own ESI fleets.

Changed

- Manual FAT function limited. It is only available when the FAT link has been
created within the last 24 hours and has not been re-opened.
- Message templates refactored to make them more maintainable

Changed

- Ability to manually add pilots to FAT link has been disabled for ESI tracked FAT
links. The reason for this is pretty simple. Since an ESI tracked FAT link is
continuously tracking the fleet via ESI, all pilot who have been in said fleet are
added automatically. If someone hasn't been added, said someone wasn't in the fleet.

⚠️ Important ⚠️

If you haven't updated to the v2 version yet, do so first and do not go straight to
this version. Read the [update instructions for v2.0.0 please](-update-instructions-for-v200-)
please.

Fixed

- `django.db.utils.IntegrityError: (1048, "Column 'log_time' cannot be null")` on
log merge.

⚠️ Important ⚠️

If you haven't updated to the v2 version yet, do so first and do not go straight to
this version. Read the [update instructions for v2.0.0 please](-update-instructions-for-v200-)
please.