feat(one-app): removed tenancy or tenant instances

[NarmeenNaveedAhmed]

Description

This PR is for removing/replacing(where needed) all the instances of tenancy and tenant.

Motivation and Context

This is to ensure consistency in the code base and to keep it generic.

How Has This Been Tested?

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 not work as expected)
• Documentation (adding or updating documentation)

Checklist:

• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• This change requires cross browser checks.
• Performance tests should be ran against the server prior to merging.
• This change impacts caching for client browsers.
• This change impacts HTTP headers.
• This change adds additional environment variable requirements for One App users.
• I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using One App?

The idea is to keep it as generic so specific keywords like tenant or tenancy do not cause any confusion for developers.

[CLAassistant]

All committers have signed the CLA.

[oneamexbot]

📊 Bundle Size Report

file name	size on disk	gzip
app.js	112.6KB	31.4KB
runtime.js	15KB	5.3KB
vendors.js	128.4KB	38KB
app~vendors.js	405.9KB	105.9KB
legacy/app.js	119.4KB	33KB
legacy/runtime.js	15KB	5.3KB
legacy/vendors.js	163.4KB	44.9KB
legacy/app~vendors.js	412KB	107.6KB

Generated by 🚫 dangerJS against cd0c9f6