first handle all integer properties, then all double ones

this is required in situations where double grid properties depend on
the values of integer (i.e, *NUM) ones which appear later in the
deck. Example:

```
PROPS

SWU
* /

REGIONS

SATNUM
*2 /
```

the default value of the SWU keyword depends on the value of the
SATNUM property which only gets defined later in the deck. an
alternative to the approach of this patch would be to process the
grid properties of the REGIONS section before the others. I'm a bit
indifferent which approach is better...
Merge pull request #294 from andlaus/GridProperties_first_int_then_double

first handle all integer properties, then all double ones
fix compiler warnings and rename CF to ConnectionTransmissibilityFactor

for the compiler warnings, see e.g.

https://opm-project.org/CDash/viewBuildError.php?type=1&buildid=27777

the CF to ConnectionTransmissibilityFactor rename makes things much easier to
understand for people who are not intimately familiar with the wells
code.
Merge pull request #300 from andlaus/fix_warnings

fix compiler warnings and rename CF to CompletionFactor
EclipseState: provide an accessor method for the unit system used by the deck

this is required to convert calculated quantities to the same units as
the ones used in the input deck.
Merge pull request #301 from andlaus/EclipseState_export_unit_system

EclipseState: provide an accessor method for the unit system used by the deck
Fixed dimension of Kh item to Permeability*Length
remove the 'ParserBoolItem.[ch]pp' files

they were empty and as far as I can see, Eclipse does not have the
concept of boolean items...
DeckItem: add indices to the methods which allow to query the defaulted status

also, this renames DeckItem::setInDeck() to DeckItem::wasSetInDeck()
because the former method can easily be confused with a setter method
(which it is not, it is a 'getter').

note that there is a small semantical difference now: the old
signatures specified the status of the whole *item* while the new
variants are specific for a single *data point* of an item. Though at
this point the index passed to the methods is still disregarded..
make the defaults of an item settable per data point

instead of for the whole item...
make ParserItems always defaultable

i.e. remove the defaultSet() method and its friends. this is required
to be able to specify defaults in DATA items like grid properties or
saturation tables. e.g.

SGL
10*0.1 10* 10*0.2 /

would not be possible without this. If no meaningful default for an
item is defined, float and double items get NaN, int items get -1 and
string ones get an empty string. The hope is that if these values get
used in the simulation, they will make the result obviously
incorrect. (Whether a data point of an item was defaulted can be
queried using item->defaultApplied(index).)
add more explicit unit test for defaulted deck items

(the ParserItemTests already have one (Scan_All_WithDefaults) but a
second one won't hurt...)
add some defaulted values to the unit test of PVTG
remove the "value status" concept from deck items

I know it was only added recently, but all of the "setInDeck()" calls
can now be substituted by a combination of item->size() and
item->defaultApplied(index)...
extend "StarToken" class

that's because not every token which contains a star represents an
repetion, e.g.

'PROD*'

and

'123*456'

(with the quotes) are strings...
ParserItem: improve the equallity testing code and remove the defaultSet() method

but we still need the m_defaultSet member because NaN == NaN as well
as NaN != NaN...
Merge pull request #302 from andlaus/improve_defaults_handling

Improve defaults handling
Deck: mark numKeywords() and getKeywordList() as const

this was probably an oversight...
add the ROCKOPTS keyword

because to properly initialize the ROCKTAB table, it is required...
add the IMPTVD and IMKRVD keywords and table classes

basically they are just renamed copies of the EN* variants...