Bug: Multiple top-level targets with the same name and architecture result in invalid `swift_debug_settings.py`

Describe the bug

When we generate swift_debug_settings.py, we map settings for top-level targets to an lldb_context_key. This key is comprised of a versionless target triple plus the executable name. So if two targets generate the same key, only one of them will have their settings written to swift_debug_settings.py, and both will use those settings. This can result in broken debugging.

Expected behavior

The debug settings are correctly set for each top-level target.

Additional context

I don't believe we have any additional information that we can use in the StopHook to make the key have higher fidelity, which means that we will either have to:

• Generate different versions of swift_debug_settings.py and use the correct one depending on which target is being debugged
• Generate a single swift_debug_settings.py, with higher fidelity keys in _SETTINGS, and pass in some information in the stop hook's extra_args in order to adjust the key we generate

I would like to do the second one if possible.