core: expose `is_source` on `MovementHistoryListBrain`

This can be useful when making a report on movements and when we list
properties of the movements that depend on the side but are not
directly exposed on MovementHistoryListBrain. One use case was
`Movement_getSpecificReference`, which shows `source_reference` when
the brain is for the source and `destination_reference` otherwise.

With this new approach, instead of guessing we record the "is_source"
information at indexing time, when we know this for sure.

This also simplifies `MovementHistoryListBrain.date` and
`MovementHistoryListBrain.mirror_date` which no longer need to guess
the side and fix a problem that because this guessing was done using
`movement.getSourceUid()` - which cause security errors when users can
not access the source of the movement.
12 jobs for feat/brain_is_source in 0 seconds
Status Job ID Name Coverage
  External
passed ERP5.CodingStyleTest-TestRunner1

01:51:23

passed ERP5.PerformanceTest-TestRunner1

00:26:46

failed ERP5.UnitTest-TestRunner1

03:44:10

failed ERP5.UnitTest-Zope2-ForTestRunner1

02:49:50

passed ERP5.CodingStyleTest-TestRunner1

01:07:29

passed ERP5.PerformanceTest-TestRunner1

00:26:45

failed ERP5.UnitTest-TestRunner1

02:01:53

failed ERP5.UnitTest-TestRunner1

02:10:37

failed ERP5.UnitTest-TestRunner1

01:53:26

failed ERP5.UnitTest-Zope2-ForTestRunner1

01:50:41

failed ERP5.UnitTest-Zope2-ForTestRunner1

01:53:36

passed ERP5.UnitTest-Zope2-ForTestRunner1

01:44:58