Replace DefaultServerCapabilities with NewDefaultServerCapabilities()…

[thedevop]

… to avoid data race

In tests, Capabilities maybe altered. However, DefaultServerCapabilities is a single global instance, where it maybe embedded in running server instances. So when value is altered, tests may fail with data race issue.

Here is an example:
In TestServerProcessSubscribeACLCheckDenyObscure:

server/server_test.go

Lines 2790 to 2794 in 65c7853

	func TestServerProcessSubscribeACLCheckDenyObscure(t *testing.T) {
	s := New(&Options{
	Logger: logger,
	})
	_ = s.Serve()

and TestServerClearExpiredRetained

server/server_test.go

Line 3328 in 65c7853

s.Options.Capabilities.MaximumMessageExpiryInterval = 0

are seemingly different tests, but they cause interferences and resulted in data race issue.

This surfaced in the failed test for PR #359.

Note, this is mostly a test issue, as normally one would (should) not alter server capabilities once server started serving.

This may also be the cause for data race issue seen in #200.

[coveralls]

Pull Request Test Coverage Report for Build 7773058128

• 0 of 18 (100.0%) changed or added relevant lines in 1 file are covered.
• 6 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-0.1%) to 98.648%

---

Files with Coverage Reduction	New Missed Lines	%
server.go	6	99.14%

Totals
Change from base Build 7495506564:	-0.1%
Covered Lines:	5545
Relevant Lines:	5621

---

💛 - Coveralls

[mochi-co]

This is a very nice fix, thank you @thedevop. I really like what you've done here.