Hindcast support: `BTK_END_DATE` (will determine a better name)

[wwlwpd]

It would be very convenient for hindcasting activities to support a way to specify a "ideal" end date for the best track that corresponds with the last record or a record before the end of records; if BTK_END_DATE falls outside of the last record that is found, adust BTK_END_DATE to fall within that date boundary.

[carolakaiser]

That would be convenient. It would help to avoid changing the input files for customized needs. Thanks for the suggestion.

[wwlwpd]

I think this issue will turn into a "add the variables needed to make hindcasts much easier to define" and will be prioritizing it.