[tests-only] set user object in LocationPicker unit tests

[individual-it]

Description

give the test a user id, so that it does not try to get it from undefined
that line was added in #6287
@janackermann is it OK to mock the user that way and reuse the existing object in getStore?

Related Issue

part of #6337

Motivation and Context

get rid of error logs during unit test runs

    console.error
      [Vue warn]: Error in v-on handler (Promise/async): "TypeError: Cannot read property 'id' of undefined"

      found in

      ---> <OcButton>
             <OcGrid>
               <Anonymous>
                 <Root>

      at warn (node_modules/vue/dist/vue.runtime.common.dev.js:621:15)
      at logError (node_modules/vue/dist/vue.runtime.common.dev.js:1889:5)
      at globalHandleError (node_modules/vue/dist/vue.runtime.common.dev.js:1884:3)
      at handleError (node_modules/vue/dist/vue.runtime.common.dev.js:1844:5)
      at node_modules/vue/dist/vue.runtime.common.dev.js:1861:39

    console.error
      TypeError: Cannot read property 'id' of undefined

How Has This Been Tested?

• run unit tests locally
• 🤖

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:

Open tasks:

• ...

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information