TST/MAINT: update to pysat 3.0.0 standards, github actions

[jklenzing]

Description

Updates directory and inst_id standards to reflect new usage in pysat. Moves testing to Github Actions.

Replaces #46 and #44

NOTE that NEP 29 is not adhered to in this package (unlike the other pysat packages). The required packages build from fortran and numpy, which does not work for numpy 1.17, 1.18, and 1.19 due to issues beyond the control of the development team here. By July 2022, this versions will not be required, and it is anticipated that NEP 29 can be enforced by then.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

tested locally via

Checklist:

• Make sure you are merging into the develop (not main) branch
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• Add a note to CHANGELOG.md, summarizing the changes

[JonathonMSmith]

It's not possible to put the "--no-binary :OMMBV: pysatMagVect" here is it?

[jklenzing]

I don't think so. My nominal plan forward is to get the CI tests working again here while solving specific pysatMagVect issues in the already open issue.

[JonathonMSmith]

There is warning coming from pysat that comes up in the testing.

FutureWarning: Slicing a positional slice with .loc is not supported, and will raise TypeError in a future version.  Use .loc with labels or .iloc with positions instead.

The warning comes from the line in setitem:

 self.data.loc[key[0], key[1]] = new

This is currently at line 843 of _instrument.py in the develop branch.