Data model improvements for multi-pitch routes

[rouletout]

See also #1698 for ticking single pitches, and https://github.com/theCrag/website/issues/1769 for an alternative idea to this issue

Adding multi-pitch routes needs to be enhanced in order to get higher quality structured information and better use it in analysis and ticking. After all, why do we treat routes differently just because they are on top of each other and not next to each other.

Proposal: When entering the number of pitches information on the add route screen a set of fields should open for each indivdual pitch comprised of Pitch Number, Length, Grade, Bolts, Description, maybe Style but at least pre-populate with default and Stars

That way we will have more structured information, an easier way to tick individual pitches with different tick types per pitch and more valuable information for the climber.

[lordyavin]

Checkout the structure of Smaragdlerweg. It is documented as a sector and each pitch is a route. This makes it possible to log each pitch separately. May be this is what you are requesting but I don't want to be forced to organize my contributions alike. It would cause more effort to add new multi-pitch routes.

[scd]

I want to get through the release and see how the improvements are for logging ascents.

To do this properly needs quite a bit of analysis. One example is that I use to climb with a longer rope so often did pitches differently to what was recommended in the guidebook (for example try and do a five pitch climb in three pitches).

[Mdemaillard]

I believe the top suggestion while creating the multi-pitch is very similar in concept to the UI currently available when logging pitches info.

Allow clear input per pitch of:

• [ ] pitch number
• [ ] pitch name
• [ ] Pitch heights (new user don't know the comma delimited usage of the single field)
• [ ] Pitch grades (new user don't know the comma delimited usage of the single field)
• [ ] Pitch description
• [ ] Pitch bolts

[Mdemaillard]

Includes #640