fix: [#188172536] add userId to business object

[aadedejifearless]

Description

This PR introduces a major change by adding a userId field to the business object. This addition ensures that each business is associated with a specific user, which will support future features involving the business-user relationship. The generateBusiness method has been updated to take an argument of UserData to include the userId in the business object

Ticket

This pull request resolves #188172536.

Approach

Updated the generateBusiness method to accept UserData as an argument, allowing the userId to be added to the business object.
All instances where generateBusiness is used have been updated to reflect this change, ensuring that the userId is properly included in the business object.
This ensures consistency across the codebase and sets up the necessary foundation for future work that depends on the userId field in the business object

Steps to Test

n/A

Notes

Code author checklist

• I have rebased this branch from the latest main branch
• I have performed a self-review of my code
• I have created and/or updated relevant documentation on the engineering documentation website
• I have not used any relative imports
• I have pruned any instances of unused code
• I have not added any markdown to labels, titles and button text in config
• If I added/updated any values in userData (including profileData, formationData etc), then I added a new migration file
• I have checked for and removed instances of unused config from CMS
• If I added any new collections to the CMS config, then I updated the search tool and cmsCollections.ts (see CMS Additions in Engineering Reference/FAQ on the engineering documentation site)
• I have updated relevant .env values in both .env-template and in Bitwarden

[jphechter]

Just kindof a musing... How would y'all think about making this into an array value? This could potentially allow us to have a 1:many relationship between business:user. Maybe a little bit of YAGNI, but I could see this being a nice support feature in the future even if we don't want to work on building user permissions into the system at this present time.

@aadedejifearless @seidior