Determine the FORD version number for FORD CI document deployment

[zoziha]

Motivation

As far as I know, in both #624 and #278, the failure of FORD document deployment occurs, which is often caused by the features and version updates of FORD.
Determining the appropriate FORD version for stdlib in stages will help new contributors are less likely to face FORD CI failures due to FORD version updates.

Prior Art

stdlib/.github/workflows/doc-deployment.yml

Line 37 in c6b54e1

brew install -f --force-bottle --keep-tmp ford

We can use:

pip install -v ford==6.1.10

Additional Information

• ford crashes on module procedure with interface body in same scope Fortran-FOSS-Programmers/ford#446

[awvwgk]

There is some historical baggage on the documentation workflow, see #289. It might be time to revisit the workflow and use a different setup strategy.

[zoziha]

Currently stdlib publishes FORD documents based on macOS and brew, while fpm publishes FORD documents based on Ubuntu and pip, it seems to use pip to install ford and publish docs is easier, maybe we can update stdlib's docs CI with fpm's CI.

[jvdp1]

I think it makes sense to use the same strategy in all Fortran-lang projects regarding ford.
@zoziha would you like to open a PR with a new strategy?