Problem
How does tour module deal with languages? For one it has language codes in the .yml filenames and it has langcode properties in the tour files, but then it does not actually export a tour langcode in .yml (fixing that in #1935000: Some configuration entities are created as in language unknown). I don't understand why does it include a language code in the yml filename? If it would want to ship with translations for tours, it should use the config translation system (locale.config.fr.$tour_name.yml for French, etc.), that would only contain translations of parts of steps that are to be translated.
Proposal
Figure out what languages do in filenames and what is the plan for tour translations.