Initialize altitude constraint from profile

According to your documentation this doesn't seem possible.

I have an astropy table with zenith and azimuth columns containing measurements of the horizon profile as seen from an observatory.

I would like to define the altitude constraint for my observation by using the measurements values.

The implementation of this might be done in this way:

- add a new method `.from_table()` to the `AltitudeConstraint` class to load the table
- modify the class constructor in a way that if a table is defined instead of `min`/`max` values, than the max altitude value is given by the zenith profile
- modify `AltitudeConstraint.compute_constraint` to account also for the azimutal progression of the transit

Start with the AltitudeConstraint class and its compute_constraint method, then review the documentation referenced in the issue. Determine how an astropy table containing zenith and azimuth measurements should be loaded and how the profile should affect altitude over azimuth. Done means a table-based constraint can be defined and applied across the azimuthal progression.

Written by the indexing model from the issue text.