Update workspace-init.sh to fix dev environment initialization

[sidmohanty11]

Proposed changes

While running the app-server.sh from bin directory, it enters workspace-init.sh as its inside bin so firstly we need to go only one level up to reach the lib directory to run the initInstance.js command. Then when we come back to app-server.sh all the paths are written considered relative to bin directory. So after we finish the initInstance call we can go back to bin directory to finish all the other commands.

Now (with an empty workspace or .zowe folder missing - new dev install):

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Change in a documentation
• Refactor the code
• Chore, repository cleanup, updates the dependencies.
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

PR Checklist

Please delete options that are not relevant.

• If the changes in this PR are meant for the next release / mainline, this PR targets the "staging" branch.
• My code follows the style guidelines of this project (see: Contributing guideline)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• New and existing unit tests pass locally with my changes
• video or image is included if visual changes are made
• Relevant update to CHANGELOG.md
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works, or describe a test method below

Testing

Further comments

[DivergentEuropeans]

Thanks @sidmohanty11 Great change but solved by #257