Component statement support for <children> and field attributes

[iObject]

No description provided.

[TwitchBronBron]

Looks pretty good!

I'd like to see some unit tests to verify these features work and ensure they continue to work in the future. You can add them in ComponentStatement.spec.ts and follow this existing test's model:

brighterscript/src/parser/tests/statement/ComponentStatement.spec.ts

Lines 327 to 348 in 086e267

	it('adds private methods to codebehind as plain functions', async () => {
	program.setFile('components/ZombieKeyboard.bs', `
	component ZombieKeyboard
	private sub init()
	'test
	end sub
	private sub doSomething()
	print "do something"
	end sub
	end component
	`);
	await testTranspile(program.getFile('components/ZombieKeyboard.codebehind.brs'), `
	sub init()
	'test
	end sub
	sub doSomething()
	print "do something"
	end sub
	`);
	});

Let's add at least one for each annotation type, but feel free to do more with variations on the annotation (like what happens if the annotation is present but missing the string for example). Maybe test a few with several annotations present at the same time, that type of thing.

You run them by calling npm run test:nocover or by using the test task in vscode.