DatePicker lock on membership field [Transaction screen]

**Describe the bug**
In the case that a member only pays the month they will come to the space, there usualy is a conflict between the current date of doing our administrative work and the new experation date of the member.

Example: member pays on the 7th of august to extend their membership to the 1st of september, but the finances were done of the 6th of august. this means that we will only see it the next month. When we than see it and try to adjust this in the system we most likely past the 1st of september....

We will then not be able to set the correct date in the transaction screen. we have to put it on the first of october to adjust it through the member list window.

Furthermore, if you use a wrong date like for example the 16th of september the system crashes

**To Reproduce**
Steps to reproduce the behavior:
1. Go to make a new transaction
2. use for example the 'Jan Van Sweevelt' user
3. Let him pay his membership fee
4. try to set the date to the first of the current month. (You can't)

**Expected behavior**
To just be able to select the first of this month. so maybe not lock the date picker on this date but one month in the past?

Start in the new transaction flow and reproduce the membership payment case with the Jan Van Sweevelt user. Check the date picker behavior for the first of the current month and an invalid date such as September 16; done means the valid date can be selected and the invalid-date case no longer crashes.

Written by the indexing model from the issue text.