Enable the "emit-did-peer..." startup options to be tenant specific

[swcurran]

We would like to see the new ability to emit DID Peer connections to tenant specific, so that we can experiment with enabling connection reuse.

[swcurran]

@esune , @loneil — what is the effort to do this? Are there instructions on how this is done?

[esune]

This PR has the changes that relate to per-tenant settings.
At minimum, we would extend the settings to be included/supported in the list that currently holds which settings can be "tenantized". We could also look at cleaning-up a bit that list (which is actually currently two lists) so that more settings are supported out-of-the-box without changes (probably a slightly bigger change).

[swcurran]

So the steps are:

• update the Multitenancy.md documentation to add the item tot he list
• update the admin/routes.py to add the item to the two lists

Sound right?

[esune]

Yes, that sounds about right if we just want to add this flag to the list without extra refactoring.