kicking off #20 - modernizing fastpairs

[jGaboardi]

This PR kick of #20:

• removes versioning from setup.py that was causing an error – remove portion of setup.py to allow for install #23
• adds an initial CI environment and workflow for testing – with a pinned scipy=1.11 – [COMPAT] fastpairs not compatible with scipy>=1.12 #22
• CI tests pass in my fork
• The action will only run in this fork once merged

Important

@carsonfarmer Perhaps before merging this PR:

• We should tag the current main with fastpair==0.1.0 to give a good point-in-time break
• Then I can update this PR and add back in a simple version=0.1.0 into the setup.py
• Once pyproejct.toml & setuptools-scm are adopted as described in interest in modernizing? #20, versioning will be automated by manual tagging.

[carsonfarmer]

Ok, I kicked off a tag (https://github.com/carsonfarmer/fastpair/tags) (and release) based on fastpair==0.1.0 (I'm not used to that x==y convention, so hopefully I did that right?).

[carsonfarmer]

Why the cron here?

[jGaboardi]

Run nightly CI on main.

[jGaboardi]

fastpair==0.1.0 (I'm not used to that x==y convention

LOL whoops. That was simply my shorthand for meaning version 0.1.0; I should have been more clear.

I'll update the tag and release as v0.1.0. We'll start using the vX.Y.Z convention, as it is useful in pushing tags that kick off automated actions. See example here.

[carsonfarmer]

👍 LGTM

[carsonfarmer]

I generally follow the convention of, if you get a 👍 then you can merge your own PRs. Is this a good convention for you too?

[jGaboardi]

I generally follow the convention of, if you get a 👍 then you can merge your own PRs. Is this a good convention for you too?

I can get on board with that.