Question on EDR: a plant may have one or more harvesting seasons
I would tend towards a one-to-many relationship between Plants and Harvests.
i.e. the Harvests table has a foreign key to Plants allowing as many harvests as desired.  The Harvests table would have all the details relating to a single harvest, such as Start Date, Minimum Duration of Harvest, etc.
I'd combine the two green tables.  If the start date for one harvest is earlier than the start date for the 2nd harvest, then that's just showing them correctly ordered in the presentation layer (i.e. by an ORDER BY clause on StartDate).
I've created a simple fiddle to show you how I'd implement the design here.
This is the DDL:
CREATE TABLE plant(
    plant_id INT AUTO_INCREMENT,
    taxon_name VARCHAR(25),
    common_name VARCHAR(25),
    PRIMARY KEY (plant_id)
);

CREATE TABLE harvesting_req(
    harvesting_req_id INT AUTO_INCREMENT,
    plant_id INT,
    number_of_harvests INT,
    harvest_start_date DATE,
    PRIMARY KEY(harvesting_req_id)
);

ALTER TABLE harvesting_req 
ADD FOREIGN KEY(plant_id_fk) 
REFERENCES plant(plant_id) ON DELETE SET NULL; 

JOINing the tables looks like:
SELECT p.taxon_name
    , p.common_name
    , hr.*
FROM plant p
    INNER JOIN harvesting_req hr ON p.plant_id = hr.plant_id;

The output looks like:




taxon_name
common_name
harvesting_req_id
plant_id
number_of_harvests
descriptive_growing_season
min_length_of_growing_harvest
max_length_of_growing_harvest
harvest_start_date




Taraxacum
dandelion
1
1
2



2021-04-15


Taraxacum
dandelion
2
1
3



2021-07-01




I'm not convinced you need a number_of_harvest column in the harvesting_req table since you'd have a row per harvest.