Twilio - Option to Give Each call a Fresh History

[SanderGi]

Task: https://app.asana.com/0/1203067047205953/1207977643971933

Q/A checklist

• If you add new dependencies, did you update the lock file?

poetry lock --no-update

• Run tests

ulimit -n unlimited && ./scripts/run-tests.sh

• Do a self code review of the changes - Read the diff at least twice.
• Carefully think about the stuff that might break because of this change - this sounds obvious but it's easy to forget to do "Go to references" on each function you're changing and see if it's used in a way you didn't expect.
• The relevant pages still run when you press submit
• The API for those pages still work (API tab)
• The public API interface doesn't change if you didn't want it to (check API tab > docs page)
• Do your UI changes (if applicable) look acceptable on mobile?
• Ensure you have not regressed the import time unless you have a good reason to do so.
  You can visualize this using tuna:

python3 -X importtime -c 'import server' 2> out.log && tuna out.log

To measure import time for a specific library:

$ time python -c 'import pandas'

________________________________________________________
Executed in    1.15 secs    fish           external
   usr time    2.22 secs   86.00 micros    2.22 secs
   sys time    0.72 secs  613.00 micros    0.72 secs

To reduce import times, import libraries that take a long time inside the functions that use them instead of at the top of the file:

def my_function():
    import pandas as pd
    ...

Legal Boilerplate

Look, I get it. The entity doing business as “Gooey.AI” and/or “Dara.network” was incorporated in the State of Delaware in 2020 as Dara Network Inc. and is gonna need some rights from me in order to utilize my contributions in this PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Dara Network Inc can use, modify, copy, and redistribute my contributions, under its choice of terms.

[SanderGi]

@devxpy, I don't think adding id in user_id_fields is correct logic. It counts my missed calls convos as separate users and over counts slack users by also counting personal channels:

I believe the reason it was changed to include id in the id fields is to make the unique_user_id function work for get_display_name so I've changed it to only include id for this special case. Lmk if this has any side effects that I have missed

[devxpy]

@devxpy, I don't think adding id in user_id_fields is correct logic. It counts my missed calls convos as separate users and over counts slack users by also counting personal channels: I believe the reason it was changed to include id in the id fields is to make the unique_user_id function work for get_display_name so I've changed it to only include id for this special case. Lmk if this has any side effects that I have missed

makes sense, will test and revert