[MRG] Print survey link upon first launch of GUI or first import

[sketch123456]

This PR is in regard to issue #1141 .

There is no reliable way to print a message after the user runs pip install that works across all installation methods. It may be done if the user runs the verbose install (pip install -v), but this may not be entirely user-friendly.

As such, my approach to this problem was to print a link to the survey upon the first successful import or the first successful launch of the GUI.

1. First Import: When a user runs import hnn_core, the message is displayed via hnn_core/__init__.py
2. First GUI Launch: When a user runs hnn-gui without importing the package directly, the message is displayed via hnn_core/gui/__init__.py

A persistent config file ~/.hnn_core_config.json ensures the message is only shown once, regardless of which interaction path the user takes first.

Changes Made:

1. Created hnn_core/_first_run.py containing the check_first_run() function that:

• Checks if ~/.hnn_core_config.json exists
• Prints the survey message if this is the user's first run
• Creates the config file to mark that the message has been shown

2. Updated hnn_core/__init__.py to call check_first_run() to catch first import scenarios
3. Updated hnn_core/gui/__init__.py to call check_first_run() to catch first GUI launch scenarios

Both implementations wrap the check in try-except blocks to ensure that any errors in displaying the message don't break core functionality.

[asoplata]

Thanks Karthikeya, unfortunately you seem to be correct, in that pip doesn't appear to have support for a "post-install message" that is separate from the potentially large amount of -v verbose output. I'll ask the dev team what we think about the solution of adding a hidden config file. If we decide that we don't want to spawn such files, we may end up deciding to cancel this feature request. I'll let you know, thanks for your work!

[asoplata]

@sketch123456 , I have finished going over your PR and making some changes. Thanks for your contribution! I think it's now ready for review by our other developers.

I've made some changes to the code, but mostly only minor things. However, in order to resolve some merge conflicts, it was easiest to "rebase" the branch, which I have done remotely. In other words, if you want to check out your branch locally on your computer, the history on origin has been changed, and you must delete (or overwrite) your local branch. You can find some guidance on how to do this at our Contributing Guide here https://jonescompneurolab.github.io/hnn-core/stable/contributing.html#keeping-your-code-up-to-date-by-rebasing

[asoplata]

@ntolley @dylansdaniels This is now ready for review by another member of the team (since I edited a bunch of the code). The "flag" file for the survey is now saved to, essentially, <environment>/<python-version>/site-packages/hnn_core/survey_seen.json.

[asoplata]

This will resolve #1141 .

[asoplata]

This was reviewed in a group Code Review meeting either last week or the week before. Merging after I add in a circleci fix commit.