Use BMI version in module name

This PR introduces an interesting change to the Fortran BMI specification. To prevent collisions between BMI versions, I've appended the Fortran BMI version to the name of the module. So, what was

module bmif

is now

module bmif_1_2

where 1.2 is the BMI version. When compiled, this will produce the module file bmif_1_2.mod. Here's the updated tree of the install:

./
├── include
│   └── bmif_1_2.mod
└── lib
    ├── libbmif.so -> libbmif.so.1.2
    └── libbmif.so.1.2

Advantages of this approach:

It doesn't use an unorthodox install path.
It will be easy to see which version of the BMI is used.
It shouldn't matter if the module file gets clobbered by another model's install
Multiple BMI versions can exist
It will work with either the user copying the BMI spec file to their build or the user installing the bmi-fortran package through conda

Disadvantages of this approach:

It's awkward-looking.
The user needs to import bmif_1_2 instead of bmif.

Note that I also revised the cmake build process, since I keep learning more about cmake.

cc @wk1984 & @rmcd-mscb for opinions. h/t @mgalloy for this idea.

csdms / bmi-fortran

Use BMI version in module name #36