Contribute to debug start experience

Hi VS Code dev here 👋

Last milestone we have introduced a Start View for debugging. More about this can be found here https://github.com/microsoft/vscode/issues/84677
So when the user has no launch.json file this view should help him start debugging.

This view is currently language agnostic and not very cluttered thus we are slowly looking in opening it up to extensions. We have two options:

1. Allow extensions to contribute commands / text to the current view. Those commands would be rendered as additional blue buttons or as some menu
2. Allow extensions to contribute a whole view which would be below the start view. The Java extension could choose what to render in that view and it would give a bit more control to the extension. Using context keys this view would only be visible in the "start" experience

What I would be interested in is what Java would like to contribute to improve the start experience. If it is only commands, than I think it makes sense to show those commands in the start view (for example with additional blue buttons). If it is much more then it makes more sense that Java contributes the whole view.
What are the biggest pain points that Java users hit when setting up debugging?

Related python discussion: https://github.com/microsoft/vscode-python-debugger/issues/164

Let me know what you think and how you envision the Java debug start experience.
Thanks!

Current look of debug start view
fyi @testforstephen

Leia primeiro a issue vinculada do VS Code sobre a exibição de início da depuração e a discussão relacionada sobre o depurador Python; esta issue não nomeia nenhum arquivo do repositório, teste ou ponto de entrada. Identifique os problemas de configuração e depuração dos usuários de Java e, em seguida, determine se a extensão deve contribuir com comandos ou com uma exibição inteira. Considera-se concluído quando houver um design acordado para a contribuição e um follow-up com escopo definido.