Suggested fixes for pub and priv are surrounded in backticks

[jribbink]

Current Behavior

Currently, the suggested fixes for pub and priv access modifiers are surrounded in backticks (i.e. `access(all)` or `access(self)`)

This is technically not the semantically correct correction to the token and is problematic for external consumers of these suggestions (i.e. Language Server) which seek to actually apply this correction, but produce invalid Cadence when doing so.

cadence/runtime/parser/declaration.go

Lines 284 to 287 in 3adb033

	p.report(p.syntaxErrorWithSuggestedFix(
	"`priv` is no longer a valid access keyword",
	"`access(self)`",
	))

cadence/runtime/parser/declaration.go

Lines 298 to 302 in 3adb033

	p.report(NewSyntaxErrorWithSuggestedReplacement(
	pubToken.Range,
	"`pub` is no longer a valid access keyword",
	"`access(all)`",
	))

Expected Behavior

There should be no backticks. It should be up to external clients to encapsulate the suggestion in any formatting if they wish to do so as this is fairly trivial & the raw suggestion is much more important.

Steps To Reproduce

Try replacing pub or priv in VSCode extension

results in...

Environment

- Cadence version: v1.0.0-preview.1.0.20231213191345-0ff20e15e7e1
- Network: n/a