TRUNK-6203: Global properties access should be privileged

[Seremba]

Description of what I changed

Refactored getGlobalProperty API method implementation to throw an authentication exception if user is not authenticated and property requested is not on a list of anonymously-accessible global properties. built a list of global properties that need to be available anonymously for startup. List is not yet fully exhausted.

Issue I worked on

see https://issues.openmrs.org/browse/TRUNK-

Checklist: I completed these to help reviewers :)

• My IDE is configured to follow the code style of this project.

  No? Unsure? -> configure your IDE, format the code and add the changes with git add . && git commit --amend

• I have added tests to cover my changes. (If you refactored
  existing code that was well tested you do not have to add tests)

  No? -> write tests and add them to this commit git add . && git commit --amend

• I ran mvn clean package right before creating this pull request and
  added all formatting changes to my commit.

  No? -> execute above command

• All new and existing tests passed.

  No? -> figure out why and add the fix to your commit. It is your responsibility to make sure your code works.

• My pull request is based on the latest changes of the master branch.

  No? Unsure? -> execute command git pull --rebase upstream master

[dkayiwa]

@Seremba did you see the maven build failures?

[Seremba]

Yes, @dkayiwa. they have been a challenge for several days even when I ran mvn clean package but I decided to create the PR so at least I can have a way of asking for help.

[wikumChamith]

@Seremba there are a lot of formatting changes unrelated to this issue in your PR. You have created another PR for the formatting changes: #4548. That PR also contains the changes you made here. This is the wrong way of doing this.

Create separate branches from the master for both PRs and do not merge them. Can you take a good look at this: https://wiki.openmrs.org/display/docs/Pull+Request+Tips?

Every time you finish a branch and want to create another, you need to first switch to the master branch, and then create the new branch from there. If you do not do so, your pull request for the new branch will get mixed up with commits from the other branch