Created ScopeData for Julia's Scope

[B-rando1]

I created ScopeData, which is intended to hold information about a variable's scope. I also switched Julia's ScopeSym representation to use it.

Currently nothing is done with it, but I believe we need to integrate it into the AST for Julia, so that we can get the information back out of the variable as needed.

Contributes to #3821

[JacquesCarette]

While this seems reasonable, as it is built on top of a PR that I'm not sure is the right way to go, I won't approve until that is investigated.

This change is quite likely independent of that one, and should likely have been done that way.

[B-rando1]

You're right, this should have been on its own branch from the start. I've rebased it to main.

[B-rando1]

I added ScopeData to the other renderers as well, abstracting the functions into their appropriate places. I was initially hoping that we could just use ScopeData in the Julia renderer where it's used, but it looks like because we need it in the state, all of the renderers need to use the same type.

• We need variables' scope to be in the state so that we can extract a variable's state when creating a new variable in a few places. E.g.
  

  Drasil/code/drasil-gool/lib/Drasil/GOOL/LanguageRenderer/JuliaRenderer.hs

  Line 706 in 150ea02

  let begVar = var bName int local -- TODO: get scope from vn

[B-rando1]

I removed the Doc from ScopeData. Initially I was thinking it might be handy to add flexibility for the keyword used in global/local declarations, but now I'm thinking that might be premature. We only have one language that does these declarations, and it's hard to say if that would actually be handy if we do add another language with them.

Because the functions are all mostly shared between renderers, it would be easy to add another field to ScopeData if we want to add one later.