Start GPU porting

[EmilyBourne]

This PR is not ready to review but I want to check the cuda compiler output as the output on GPU is not verbose enough

Merge Request - GuideLine Checklist

Guideline to check code before resolve WIP and approval, respectively.
As many checkboxes as possible should be ticked.

Checks by code author:

Always to be checked:

• There is at least one issue associated with the pull request.
• New code adheres with the coding guidelines
• No large data files have been added to the repository. Maximum size for files should be of the order of KB not MB. In particular avoid adding of pdf, word, or other files that cannot be change-tracked correctly by git.

If functions were changed or functionality was added:

• Tests for new functionality has been added
• A local test was succesful

If new functionality was added:

• There is appropriate documentation of your work. (use doxygen style comments)

If new third party software is used:

• Did you pay attention to its license? Please remember to add it to the wiki after successful merging.

If new mathematical methods or epidemiological terms are used:

• Are new methods referenced? Did you provide further documentation?

Checks by code reviewer(s):

• Is the code clean of development artifacts e.g., unnecessary comments, prints, ...
• The ticket goals for each associated issue are reached or problems are clearly addressed (i.e., a new issue was introduced).
• There are appropriate unit tests and they pass.
• The git history is clean and linearized for the merge request. All reviewers should squash commits and write a simple and meaningful commit message.
• Coverage report for new code is acceptable.
• No large data files have been added to the repository. Maximum size for files should be of the order of KB not MB. In particular avoid adding of pdf, word, or other files that cannot be change-tracked correctly by git.

[codecov]

Codecov Report

❌ Patch coverage is 98.70690% with 9 lines in your changes missing coverage. Please review.
✅ Project coverage is 95.78%. Comparing base (3e5910f) to head (1f809c6).

Files with missing lines	Patch %	Lines
include/GMGPolar/setup.h	73.07%	7 Missing ⚠️
include/GMGPolar/utils.h	95.00%	1 Missing ⚠️
src/PolarGrid/polargrid.cpp	98.03%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #278      +/-   ##
==========================================
+ Coverage   95.76%   95.78%   +0.01%     
==========================================
  Files          79       79              
  Lines        8555     8634      +79     
==========================================
+ Hits         8193     8270      +77     
- Misses        362      364       +2     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[julianlitz]

@EmilyBourne Done

[julianlitz]

This would also be a possibility for the PolarGrid class. Store both Cpu and Gpu memory and then use ifdef to return the correct memory space value.

[EmilyBourne]

This would also be a possibility for the PolarGrid class. Store both Cpu and Gpu memory and then use ifdef to return the correct memory space value.

I'm not sure I see an advantage in this. In gysela we often run on AMD (so not cuda), this fix wouldn't work for that case. It also makes it much harder to identify what has and hasn't been ported given that the aim is to only have the GPU version of PolarGrid at the end