Light-curve-python

Fixed

- Bug introduced in v0.6.5: `*Fit.model(t, params)` wrongly checked `t` and `params` arrays to have the same length

Added

- `BazinFit` and `VillarFit` have got `ceres` and `mcmc-ceres` algorithms using [Ceres Solver](http://ceres-solver.org)
as a non-linear least squares optimizer. `ceres` is found to be more robust than `lmsder` algorithm (available
via `gsl` Cargo feature) but working roughly twice slower. Ceres can be built from source (`ceres-source` Cargo
feature, enabled by default in `Cargo.toml`) or linked to system library (`ceres-system` Cargo feature, enabled for
cibuildwheel in `pyproject.toml`)

Changed

- **API breaking:** Features' `__call__()` signature changed to make `sorted=None`, `check=True` and `fill_value=None`
arguments to be keyword-only
- **API breaking:** Features' `many()` signature changed to make all arguments but the first `lcs` to be keyword-only
- **API breaking:** `Bins` constructor signature changed to make `offset` and `window` arguments to be keyword-only. For
Rust implementation `__getnewargs__` is replaced with `__getnewargs_ex__`. Please note that for the specific case of
Python implementation and Python version < 3.10, `Bins` still accepts positional arguments
- **API breaking:** `BazinFit` and `VillarFit` constructor signatures changed to make everything but the first `lcs`
argument to be keyword-only
- **API breaking:** `Periodogram` constructor signature changed to make all arguments to be keyword-only
- **API breaking:** `DmDt` constructor signature changed to make all arguments but `dt` and `dm` to be
keyword-only, `__getnewargs__` is replaced with `__getnewargs_ex__`. `DmDt.from_borders` class-method constructor has
all arguments to be keyword-only
- **API breaking:** `DmDt` methods' signatures changed to make all arguments but data (like `t`, `t, m` or `lcs`) to be
keyword-only
- **Build breaking:** building with Ceres Solver (`ceres-source` Cargo feature) is now a default, and potentially could
break a building pipeline in some cases. If you want to build without Ceres Solver, you need to explicitly disable
default features with `--no-default-features` maturin flag
- CI: switch from `macos-11` to `macos-latest` for testing
- Bump `pyo3` 0.17.3 -> 0.18.1
- Bump `rust-numpy` 0.17.2 -> 0.18.0

Removed

- **Build breaking:** `fftw-static`, `fftw-dynamic`, `mkl` Cargo features are removed after deprecation in v0.6.2 and
replaced with `fftw-source`, `fftw-system` and `fftw-mkl`.

Fixed

- Bug introduced in v0.6.5: `*Fit.model(t, params)` wrongly checked `t` and `params` arrays to have the same length

Fixed

- Reduce Rust-Python inter-op cost for numpy arrays significantly. It dropped from ~4 μs per array to ~
100ns. https://github.com/light-curve/light-curve-python/pull/174

Added

- Initial `copy` and `pickle` (minimum protocol version is 2) support for feature extractors
and
`DmDt` https://github.com/light-curve/light-curve-python/issues/103 https://github.com/light-curve/light-curve-python/pull/145 https://github.com/light-curve/light-curve-python/pull/150
- `serde` v1 and `serde-pickle` v1 Rust dependencies. `serde-pickle` is an arbitrary choice of a (de)serialization
binary format, but it could be useful in the future having a way to inspect Rust structures from
Python https://github.com/light-curve/light-curve-python/pull/145

Changed

- Build environment: minimum support Rust version (MSRV) is bumped 1.57 -> 1.60
- Bump `light-curve-dmdt` 0.6.0 -> 0.7.1

Fixed

- `BazinFit` and `VillarFit` docs are clarified for `.model()` and `ln_prior`
usage https://github.com/light-curve/light-curve-python/issues/125 https://github.com/light-curve/light-curve-python/pull/146

No changes, it was accidentally released instead of `0.6.2`