Support sub-directories within the `.jupyter/personas` folder

[srdas]

Issue

PR #1443 locates personas with all related files inside the .jupyter/personas/ folder instead of the .jupyter folder. However, if there are multiple personas with similar file names, this will create conflicts in the new .jupyter/personas/. For example, many existing personas have a file names persona.py and the current design in PR 1443 does not accommodate separate personas with common file names.

Proposed solution

• Enable subfolders for each persona under the .jupyter/personas/ subfolder.

• We also need to add documentation to (i) explain where the files need to be placed, (ii) explain that the dependencies also need to be installed if the persona is just being "dropped in" to the proposed .jupyter/personas/<persona_name> folder.

[andrii-i]

Thank you for creating this issue @srdas. Existing personas you are referring to are personas published as a Python package which necessitates certain folder structure.

Same requirements don't apply to local personas so I think default local persona creation experience should not be defined by these requirements and instead should be as minimal as possible. And dropping in a single file provides exactly that.

Some other considerations about this:

• We could potentially add logic that you are suggesting to make it easier for people who work with packaged personas to drop them in as local personas but a) I'd imagine this to be a pretty niche user flow b) they can just rename persona.py to PERSONANAME_persona.py while dropping in the file
• file names don't really matter other than for file finding logic, Python classes inside the files are what is actually instantiated and need to have unique naming

[srdas]

@andrii-i Sounds good! I suppose renaming the persona to avoid conflicts works as well.

[andrii-i]

Supporting sub-directories might make sense for better organization of local personas