Split `profile_name` in the `profiles_table` about tulipaenergymodel.jl

[suvayu]

split rename according to source or context, since the same profile maybe used in different places

[greg-neustroev]

We had a discussion and the conclusion was that the profiles can in principle be reused, therefore multiple profile_name and profile_type combinations can use the same profile. Thus, a profile needs an identifier of some kind, either an abstract ID, or better, a descriptive name. Please note, that this name SHOULD NOT tell how the profile is used, but rather where it came from. In the Norse pipeline example, e.g., it should not be availability-Asgard_Solar, but solar_two_seasons, and then we link the availability of solar in Asgard to this profile. solar_two_seasons indicates the data origin: it is a synthetic dataset generated so that there are two seasons.

[clizbe]

From my understanding, this is how it currently works, we just need to change the profile_names in the test files, to follow @greg-neustroev 's convention above. Is that right?