Animal model update: date of entry/date of leaving

[fedjo]

We need to add 3 fields in the Animal model

• entry_date
• leaving_date
• previous_owner [optional] (string)

Moreover, this leads to update the animal view on UI using the following columns (detailed views)

Note: Columns ,so far, cannot be modified (hide/show)

| National ID | Sex | Breed | Date of birth | Birth farm number | Date of entry | Date of leaving | Animal group | status |
| FR 35 5172 6473 | F | 43 | 28/07/2022 | FR 56 127 755 | 28/07/2022 |   | Armoricaine | active |
| FR 35 5172 6488 | F | 43 | 02/09/2023 | FR 22 489 775 | 22/04/2024 |   | Armoricaine | active |
| NL 1234569 | M | 56 | 01/02/2024 | NL 0001234567 | 27/02/2024 | 15/06/2024 |   | inactive |

[arruda]

@fedjo I just realized while modeling this changes that we need to first confirm with the user if we want to keep a record of multiple entry/leaves of a single animal, or if there will be only one record for the animal entering/leaving the farm.

I think that if one animal can be lent multiple times to one farm, then it would make sense to keep track of all these movements (entry/exit).

And if that's the case, then I believe this field will only make sense once we have the farm calendar activities for the animals (#67).
Then it could be done as:

• user registers purchase/lent of caw, from farm X, on day Y.
• Then this date Y is used to update the entre date field of that animal (while for the user this field entry-date field in the animal is read-only).
• Later, creating a selling/leaving animal calendar activity will set the leave date in the animal to be the one set in the leave activity.
• if later on date Z the same is "rented"/lent again, then another activity for this animal entry is created and the the date Z becomes the new entry date in that animal (and leave date is reset do null).
  Alternativelly I can add now the fields, but they won't make much and be of much use until the activities to manage the I/O of animals are ready