Don't set target feature version to default if it is already set

[kysmith-csg]

Previously, editing a target feature location would always set the version to 1.0.0.qualifier, even if the version was set already. This is because this initialize() method is called after the feature details are filled in.

Now, editing an existing feature will fill in the details as shown in the target file. New features will continue to be set to 1.0.0.qualifier.

[github-actions]

Test Results

  214 files  ±0    214 suites  ±0   21m 11s ⏱️ + 4m 0s
  664 tests ±0    654 ✅ +1  10 💤 ±0  0 ❌  - 1 
1 328 runs  ±0  1 306 ✅ +1  22 💤 ±0  0 ❌  - 1 

Results for commit 839548c. ± Comparison against base commit 60e66ff.

♻️ This comment has been updated with latest results.

[laeubi]

looks reasonable

[laeubi]

@kysmith-csg you need to bump the version of the affected bundle.

[kysmith-csg]

@kysmith-csg you need to bump the version of the affected bundle.

Done, sorry about that.

[HannesWell]

@kysmith-csg is this not relevant anymore?

[kysmith-csg]

@HannesWell it is still valid. I went to Github to update my fork and I completely forgot this pull request was open still. Luckily I still had the commit locally :)

[HannesWell]

@HannesWell it is still valid. I went to Github to update my fork and I completely forgot this pull request was open still. Luckily I still had the commit locally :)

No problem, I think that's the reason why it is recommended to use topic-branches for PRs 😅
But in order to prevent further disturbance lets submit this, it looks good.
Thanks for this contribution.