Suggested enhancements to extraction refactoring

[StephenWeatherford]

Pulled from #14701

• Add telemetry for which options are used Add telemetry to extraction menu choices #15234

• Consider blocking some specific scenarios (this could be added to in the future) #15260

• Add newline before/after new declaration (preferably if not already blank) Be smart about newlines before/after extractions #15194

• Suggestion: Extraction menus: If no existing params/etc, insert new ones at top of file in appropriate place #15261

• [@anthony-c-martin]

There are a few places where an object can't be substituted (module body & resource body AFAIK, but there may be more). We should block it here (cursor == |)

resource namespace 'Microsoft.EventHub/namespaces@2024-01-01' existing = {|
  name: 'askdjfh'
}

• [@anthony-c-martin]

Another place we should block the action:

resource eventHub 'Microsoft.EventHub/namespaces/eventhubs@2024-01-01' = if (|foo != null) {
  parent: namespace
  name: foo!
}

• [@anthony-c-martin]

Technically it's not doing anything wrong here, but I'm wondering if we should block extracting a variable reference into a variable, because it's a bit odd:

var test = ''
var test2 = t|est

• [@anthony-c-martin]

"Extract parameter" generates invalid code here:

var test2 = {}
var test = |test2

• [@anthony-c-martin]

In this case:

var thing = ''



var test2 = {|
  value: {
    
  }
}

I get the following:

var thing = ''
var newVariable = {
  value: {}
}

var test2 = newVariable

It looks like it appends directly under the previous declaration, which felt a little bit surprising. The behavior which I think would feel most intuitive to me would be prepending, but with a double new-line gap - e.g.:

```bicep
var thing = ''

var newVariable = {
  value: {}
}

var test2 = newVariable

[StephenWeatherford]

Fixed the newline issues. Moved the other issues to separate bugs.