Add managed project to import wizard project view field

[brian-mcnamara]

Checklist

• I have filed an issue about this change and discussed potential changes with the maintainers.
• I have received the approval from the maintainers to make this change.
• This is not a stylistic, refactoring, or cleanup change.

Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.

Discussion thread for this change

Description of this change

This change adds either a default or adds to the history the projects .managed.bazelproject file if it exists. This helps users who are importing the project though the wizard to find this file

[brian-mcnamara]

Switched over to adding new radio buttons in the wizard. I'm not 100% on the descriptions, so let me know if they should be updated

[blorente]

In general, I'd love to make the "choose the project view file" better. However, I have a couple of high-level thoughts:

• In our users' experience, if someone is using the managed project view, they have probably auto-imported the project, and therefore the .ijwb directory is already created for them. We don't usually check in the managed project view, because we only check it if we change something, and then we want to put it in a non-automatic place.
• I'm not sure users will understand the difference between "managed" and "env variable" and all the other options. Most users just click through this part. Could it be possible, instead, to just traverse the repository looking for project view files, have a single toggle offering those to the user? That way the user doesn't have to care about where the project view comes from.

[brian-mcnamara]

Thanks @blorente
Interesting to know, we are currently checking in a base .managed.projectview file to provide some documentation and examples as our users are new to bazel and this provides a path forward to quickly onboard. While we do mainly rely on the auto-import behavior, there is a subset of users (due to our migration strategy for our existing build system to bazel) that have auto-import disabled to prevent switch over during the migration. Because of that, the path forward for them is to use the import wizard.

As for understanding the differences, thats a fair point, and I do agree updates to clearly this and the other options makes sense. I could add the path to the file as part of the option, but let me think about other options too.

[tpasternak]

Yeah, imo it would be nice to move the new radio buttons to the bottom, and add textboxes presenting the paths (like under "Import project view file" radio button, but read-only) What do you think about it @blorente ?

[blorente]

@tpasternak I agree with your points, moving the radio buttons to the bottom and explaining which file it is is probably sufficient.

[brian-mcnamara]

Updated UI

[tpasternak]

Thank you @brian-mcnamara !