fix: backend url variable name made consistent

[TomJohnZ]

Fixed simple typo for backend ccsync url variable name

Description

Changes ManageTaskChampionCreds url setter (championApiUrl) to match CredentialsStorage url getter (ccsyncBackendUrl)

Fixes #(455)

Checklist

• Tests have been added or updated to cover the changes
• Documentation has been updated to reflect the changes
• Code follows the established coding style guidelines
• All tests are passing

[SGI-CAPP-AT2]

@TomJohnZ , This issue is already fixed by #457

[TomJohnZ]

@SGI-CAPP-AT2 Thanks for the quick response!

However, I believe #457 fixed a related, but different, issue. I am currently trying to setup ccsync and taskwarrior-flutter to work with taskchampion-sync-server; even after building and installing an APK from 7a8379f (#457), I was still encountering the issues described in #455. However, after adding the fix in this PR, the app is successfully able to sync with csync.

It is my understanding that #457 fixes a name mismatch for setting/reading the "Taskchampion sync" setting toggle.

However, this PR is fixing a name mismatch for setting/handling the "CCSync Backend URL" textbox under "Configure TaskChampion".

It seems that the PR which introduced the URL input (#429) originally used the name championApiUrl everywhere for the variable holding the backend URL. However, is appears that a reviewer requested that the variable be renamed to ccsyncBackendUrl. This was correctly changed for the getter:

taskwarrior-flutter/lib/app/utils/taskchampion/credentials_storage.dart

Line 6 in 1fe609a

static const String _apiUrlKey = 'ccsyncBackendUrl';

However, it was not updated in the setter:

taskwarrior-flutter/lib/app/utils/taskchampion/taskchampion.dart

Line 35 in 1fe609a

await prefs.setString('championApiUrl', _ccsyncBackendUrlController.text);

Therefore, this mismatch means that a "CCSync Backend URL" will not actually be saved anywhere, causing sync attempts to fail.

[SGI-CAPP-AT2]

Yeah @TomJohnZ ,
Sorry for reviewing very quick earlier.

I'll test the PR and will merge soon.

Thank you for explaining.