Updated core to 13.26.0

[papafe]

Description

Fixes #3482

[coveralls-official]

Pull Request Test Coverage Report for Build 7640121693

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.001%) to 80.957%

---

Totals
Change from base Build 7585695183:	0.001%
Covered Lines:	6405
Relevant Lines:	7787

---

💛 - Coveralls

[papafe]

@nirinchev this should fix both errors that came out from CI

• The core method get_base_url now returns a copy of the string, and not a reference as before, and now we own the assume ownership of it
• There's now an additional check done by core, that was crashing our app because the sync_route (the route to the server) was null. Added a method to set a fake route, that seems to be enough for our tests in which we create a fake local sync server. I've decided to keep it a separate method from the "GetSyncUserForTesting", but it's up for debate

[nirinchev]

I'm not sure how I feel about this - I know it's just for tests, but if this is called with one of our integration apps, it would sets its sync route to a fake value, even though a real value should exist. I don't know if sync will refresh that route at some point, but I worry that as it stands, it's possible that running this test first, then running some integration tests that use the app, those will fail due to the route being misconfigured.

[papafe]

Mmmh, I understand. Good news is that all the tests are passing now, including sync tests, so I suppose it's not a problem "yet".
If we want to be more robust for the tests we could:

• Set the fake value only if the sync route is currently empty/null
• Set it to null/empty again at the end of the test (if modified)
• Maybe create infrastructure in core to create those fake synced realm more "organically"?
  I am not sure if it's worth to do this though.

[papafe]

Given that this is the only holdup and it's only for tests, what do you think about merging this and creating a follow up ticket so we come back to it when the core investigation is finished?

[nirinchev]

Sure