Oxa/ficus update readme

[prabhanshu]

What does this PR do? Please provide some context

Updated Readme in order to get better community engagement, questions and contribution. Though it will go through thorough review from OXA teams I have just create a PR just have a look at the changes made to README file

Where should the reviewer start?

How can this be manually tested? (brief repro steps and corpnet-URL with change)

What are the relevant TFS items? (list id numbers)

Definition of done:

• [ ] Title of the pull request is clear and informative
• [ ] Add pull request hyperlink to relevant TFS items
• [ ] For large or complex change: schedule an in-person review session
• [ ] This change has appropriate test coverage
• [ ] Get at least two approvals

Reminders DURING merge

1. If you're merging from a short-term (feature) branch into a long-term branch (like dev, release, or master) then "Squash and merge" to keep our history clean.
2. If merging from two longterm branches (like cherry picks from upstream, dev to release, etc) then "Create merge commit" to preserve individual commits.

[eltoncarr]

Isn't this too much? I think we should leverage as much of the install doc/pdf as opposed to listing all the steps here.