Add "does_" columns to the software database

[rafmudaf]

This pull request removes these columns:

primary_uses:
- simulation
loads: false
- design_optimization: false
- costs: false

and adds these columns:

does_controls: false
does_costs: false
does_data_analysis: false
does_design: false
does_design_optimization: false
does_simulation: true
does_loads: false

The objective is to better represent the capabilities of each software included in this portfolio. Previously, the "primary uses" field is ambiguous since it doesn't allow for "secondary" uses that might still be relevant. Now, the list of "does_" fields are meant to capture the breadth of uses for each software. Additionally, the "does_" prefix is used to automatically create a new field in the attributes page so that all of these are shown in one column as well as split into their individual columns. That might not be clear, but I suggest to build the docs and refer to the "General" and "Full Suite Modeling Comparison" tables for more information.